In testing AOLserver 4.0.10, we seem to have discovered that the -b
command-line parameter is now required to bind to privileged ports (e.g.
80 or 443). With AOLserver 3.4.2, you could simply specify the port
numbers in the config file and AOLserver would do the Right Thing.
So two
At Friday 02:16 PM 10/7/2005, John Caruso wrote:
1) Is it true that AOLserver
4.0.10 requires -b in this circumstance, or are we just missing
something?
Ok, found this in the ChangeLog:
* Removed the child-process privleged port
Ns_SockListen
code in nsd/binder.c. Binding privleged
ports
On Fri, 2005-10-07 at 14:16 -0700, John Caruso wrote:
In testing AOLserver 4.0.10, we seem to have discovered that the -b
command-line parameter is now required to bind to privileged ports (e.g.
80 or 443).
The problem with this -B and -b stuff is that in /etc/inittab, the
process section
At Friday 04:17 PM 10/7/2005, Daniel P. Stasinski
wrote:
On Fri, 2005-10-07 at 14:16
-0700, John Caruso wrote:
In testing AOLserver 4.0.10, we seem to have discovered that the -b
command-line parameter is now required to bind to privileged ports
(e.g.
80 or 443).
The problem with this -B
Yeah, exactly. That's the number one reason why we have a web-service
starting script that knows how to start each of the different possible web
services, by service name only. But modifying that script to know which
ports and IPs every service listens on--when that information is already
