|
From: Leif M. <le...@ta...> - 2004-01-09 01:22:25
|
Mark Lassau wrote: >The wrapper is smart enough to use a different port if 1777 is already >being used by the first service, >but you may prefer to set the second service to use (eg) 1778. >This will stop unintersting log messages. > > Actually as of version 3.0.4, you can remove the wrapper.port property all together. If it is not specified, then the Wrapper will quietly allocate a port of its own choosing. The property is still there so that users can force the Wrapper to use a specific port. I wanted to get rid of it because it was not a feature that most users cared about and it is always a good idea to make things simpler where possible. Newer versions of the Wrapper do not include that property in the sample conf file any more. Cheers, Leif |