Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Artur Meski
Andrew, Mark. Thanks for the answers. Mark Page [EMAIL PROTECTED] writes: There is a new command line argument which does this: -b host:portnum But there is also option in the configuration file. When should I use configuration file, when command line option? Do this two options need to be

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Bas Scheffers
Artur Meski said: Isn't it so, that -b is only required when I want AS4.0 to bind to the privileged port? -b is never required. Simply set the http port in the config file to 80 and start the server as root with -u nsd (or whatever use you want the server to run as) Make sure this user has write

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Artur Meski
Bas Scheffers [EMAIL PROTECTED] writes: -b is never required. But AS4.0 without this option refuses to operate on port 80. Simply set the http port in the config file to 80 and start the server as root with -u nsd (or whatever use you want the server to run as) It doesn't work. Artur --

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Bas Scheffers
Artur Meski said: But AS4.0 without this option refuses to operate on port 80. You don't have another webserver currently listening on port 80, do you? (like Apache, which is usualy running by default in most linux distros) It doesn't work. Can you send the command line you are using and the

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Artur Meski
Bas Scheffers [EMAIL PROTECTED] writes: You don't have another webserver currently listening on port 80, do you? (like Apache, which is usualy running by default in most linux distros) Nope. Can you send the command line you are using and the message you get from AOLserver when you try to

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Bas Scheffers
Artur Meski said: I would like to know if it's possible to set httpport in the configuration file or I have to specify it on the command line (if it's privileged port). Well, it should be possible. And it was possible in 3.5.6, which I was using before last week. I wasn't running on a

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Brad Chick
On Tue, 2 Dec 2003 13:41:04 -, Bas Scheffers [EMAIL PROTECTED] wrote: I'll vouch for the non-restarting unless the -b flag is provided. That behavior has been consistent since the move to 4. Relatedly, it is difficult to restart aolserver, because aolserver seems to hang on to port 80. We

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Nathan Folkman
Has anyone seen this problem on Solaris? Brad Chick wrote on 12/2/03, 10:43 AM: On Tue, 2 Dec 2003 13:41:04 -, Bas Scheffers [EMAIL PROTECTED] wrote: I'll vouch for the non-restarting unless the -b flag is provided. That behavior has been consistent since the move to 4.

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Jean-Fabrice RABAUTE
Hi, Under Solaris, my AS 4.0 version needs the -b flag at startup otherwise it can't bind the port 80. It was not needed in 3.x version. What I did is change my script to add this flag to restart the server. But, after AS 4.0 is shutdown (kill -9 the second time because it hangs at

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Artur Meski
Bas Scheffers [EMAIL PROTECTED] writes: But doesn't actualy exit. I need to send it another TERM to make it exit. I've got the same problem (AOLserver 4.0, FreeBSD 4.9-RC i386). Artur -- // WWW: artur.black.pl // PGP: finger [EMAIL PROTECTED] // -- AOLserver - http://www.aolserver.com/ To

Re: [AOLSERVER] bind / privileged port

2003-12-02 Thread Tom Jackson
You have to provide the -b switch for ports under 1024 in AOLserver4.0. The ports are pre-bound while the server is still running as root. If the switch isn't provided, pre-binding doesn't happen and then later the underprivileged user can't get the port, causing the permission denied error.