On Sat, 6 Oct 2001, Stas Bekman wrote: > This patch > - picks the next available port during the configuration > - reconfigures the server at run time if after configuration, the port is > found to be used.
i would be happy to see this as an option, like '-port select', and keep the default as-is (that is: try 8529+ and stop if not available). > Now I can rebuild and test in many checkout out copies at the same time, > without wasting time specifying different port numbers for different > builds. The cool thing about my patch, that it reconfigures itself, if > somebody else took over the port after the server was configured. nice. > I've also had to fix stop() since it's OK if it tries to stop, and the > configured port is used, but there is no pid file. > > issues: > - is it a warning or an error, when we report that we use a different port? warning (or notice) with '-port select', error for the default (or -port \d+) > - default_port() is called 3 times after -clean, should I memoize the > value on the first call and return it without going through the checking > and warnings printing again and again. I think I must, since it's > possible that the default port will be released in between the calls, > and then the configuration will be broken as different places will use > different ports. sounds right. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
