russell, tom, thanks for your input.
-b 215.167.89.78:80,215.167.89.78:443
tom, this worked great. i don't know why it didn't occur to me to try
that myself!
still having to reboot twice though. i suppose i'll have to live with
that.
thanks!
mkm
--
AOLserver - http://www.aolserver.com/
I'm seeing a similar problem, but when I run AS 4.0 in the foreground
mode. I do a Ctrl-C, the server does not terminate.
However, when I do a kill -HUP, the process terminates successfully with a
Hangup message.
Sample output:
^C[09/Dec/2003:14:27:27][3798.1][-main-] Notice: nsmain:
i'm having the same problem with a little twist. i'm trying to get
nsopenssl working as well, so i need to bind to two privileged ports.
if i bind to only one port like in one of the following lines:
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g
nsadmin -b
okay, a reply to my own reply. since i had just figured out the
workaround, it didn't occur to me that i would be easier to do the
following:
instead of:
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g
nsadmin -b 216.167.89.78:80 -b 216.167.89.78:443
AND
Manish -
Depending on what you're running inside AOLserver, and your reason for
needing SSL, this may not work the way you expect. Since you're
launching 2 distinct nsd processes, one bound to each of the http and
https ports, any state that is held in the http server won't be
available if a user
On Tue, 2003-12-09 at 18:34, Manish Mukherjee wrote:
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g
nsadmin -b 216.167.89.78:80
AND
/usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g
nsadmin -b 216.167.89.78:443
I think what works is this
On Tue, 2003-12-02 at 08:24, Jean-Fabrice RABAUTE wrote:
But, after AS 4.0 is shutdown (kill -9 the second time because it hangs at
shutdownknown bug already discussed here) I can restart it within seconds
without problem.
When did this problem crop up? I just installed the GM and it
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
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
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
--
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
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
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
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
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.
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
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
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.
There is a new command line argument which does this:
-b host:portnum
Artur Meski wrote on 12/1/2003, 5:39 PM:
How can I force AOLserver (4.0) to bind to the privileged port?
Is it possible to set privileged httpport in the configuration file?
Do I have to specify it on the command
On Mon, Dec 01, 2003 at 11:39:53PM +0100, Artur Meski wrote:
How can I force AOLserver (4.0) to bind to the privileged port?
You mean port 80, or any other low number port? I think it's the same
as with AOLserver 3.x, you must start AOLserver as root, and use the
-u command line switch to tell
20 matches
Mail list logo
