BIND 10 #523: tests using ports shouldn't use same ports as running

[BIND 10 Development]

#523: tests using ports shouldn't use same ports as running
-------------------------------------+-------------------------------------
                 Reporter:  jreed    |                Owner:
                     Type:  defect   |               Status:  new
                 Priority:  major    |            Milestone:  A-Team-
                Component:           |  Sprint-20110309
  Unclassified                       |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  0.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by jreed):

 Replying to [comment:2 vorner]:
 > Hello
 >
 > The mentioned test doesn't use 5300, it uses 5321 (randomly chosen
 number somewhere nearby). Is it possible you were running two tests in
 parallel? I need to use some port number, as it is testing configuration,
 so it must be told what port to configure.
 >


 It was fixed in b9b7ef39987bc2f0031bb7f46b9002665a62607a  after this
 ticket was created.

 But yes, a system could be running the same test at same time. I don't
 know if that has happened yet.

 5321 is unassigned but is still in the registered ports. We should use a
 private port (49152 through 65535).

 > If this is a problem, I might do a heuristic ‒ bind a port without
 requesting specific one, see which one it is, close the socket and use
 that port (and hope the OS didn't give it to anybody else already).
 >
 > Should I change the default port of servers where they listen to 53? Is
 it part of this ticket as well?
 >

 No. That is tickets #617 and #618.


 > Thanks

-- 
Ticket URL: <http://bind10.isc.org/ticket/523#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development