Re: [AOLSERVER] bind / privileged port
On Fri, 2003-12-12 at 10:15, Manish Mukherjee wrote: > still having to reboot twice though. i suppose i'll have to live with > that. You might try using a boot script as simple as: -- #!/bin/bash sleep 5 export PATH=$PATH:"your extra path" export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:"your extra library path" exec /path/to/nsd $* -- Then just run the script with the same arguments as usual, instead of running nsd directly. The 'sleep 5' should be long enough. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 switch: -b 215.167.89.78:80,215.167.89.78:443 tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 starts accessing the https part of your site and vice-versa. Essentially you're running a server cluster, with all the attendant synchronisation issues... This may not be a problem, depending on the application you're running in AOLserver, but is certainly worth being aware of... cheers Russell On 10/12/2003, at 1:34 PM, Manish Mukherjee wrote: 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 /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 -b 216.167.89.78:80 do this: /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 the net result after both is the same, the second is just a little neater. mkm -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 -b 216.167.89.78:80 do this: /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 the net result after both is the same, the second is just a little neater. mkm -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 216.167.89.78:80 or /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 then i have the same issues mentioned in the previous posts - i have to stop, wait a few seconds, then restart, otherwise i get a permission denied error. however, if i try to bind to both ports: /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 or /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 -b 216.167.89.78:80 then whichever is listed first will NEVER bind, no matter how long i wait before restarting. so the only workaround that i could figure out was that in my startup script, i call BOTH lines: /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 /usr/local/aolserver/bin/nsd -t /etc/aolserver/newsite.tcl -u nsadmin -g nsadmin -b 216.167.89.78:443 -b 216.167.89.78:80 with each line, one of the ports won't be bound and the other will, but the end result is that both end up being bound. just so you know, when i started typing this post, i hadn't though of this workaround, and that's why i was posting. but midway through my typing, aha! and now it works like a charm (assuming of course i wait a few seconds after stopping). mkm -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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: AOLserver/4.0 stopping [09/Dec/2003:14:27:27][3798.1][-main-] Notice: serv: stopping server: server1 [09/Dec/2003:14:27:27][3798.1][-main-] Notice: serv: connection threads stopped [09/Dec/2003:14:27:27][3798.1][-main-] Notice: driver: shutdown complete Hangup -- Ramesh. On Mon, 8 Dec 2003, Tom Jackson wrote: > 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 doesn't > exit unless I kill -9. If I start with -ft, [ctrl]-c doesn't stop the > server, although it prints out: > [-main-] Notice: serv: stopping server: cams > [-main-] Notice: serv: connection threads stopped > [-main-] Notice: driver: shutdown complete > > It is still in control of the port as well. > > tom jackson > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with > the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field > of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 doesn't exit unless I kill -9. If I start with -ft, [ctrl]-c doesn't stop the server, although it prints out: [-main-] Notice: serv: stopping server: cams [-main-] Notice: serv: connection threads stopped [-main-] Notice: driver: shutdown complete It is still in control of the port as well. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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. Another issue is that when AOLserver restarts, sometimes it is so fast, the port isn't available, and the binding can't happen. This has been the case since before 4.0. Put in a 3-4 second delay in your startup script to fix the problem. I'm not sure I have seen the problem of killing AOLserver. Today I was starting AOLserver with sudo and I had to do [ctrl]-c twice to get back to the command line, but I don't think this is the same thing. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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
shutdownknown bug already discussed here) I can restart it within seconds
without problem.
Regards.
Jean-Fabrice.
Selon Nathan Folkman <[EMAIL PROTECTED]>:
> 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.
> >
> > Relatedly, it is difficult to restart aolserver, because aolserver
> > seems to
> > hang on to port 80.
> >
> > We have aolserver in the inittab with
> >
> > /usr/local/aolserver4/bin/nsd -it /usr/local/aolserver4/nsd.tcl -u
> > nsadmin
> > -b 209.133.111.72:80
> >
> > But when it hangs (which is often), we can't just kill all the processes,
> > because when we do, we always get:
> >
> > [02/Dec/2003:15:28:22][21164.1024][-main-] Error: nssock: failed to
> > listen
> > on 209.133.111.72:80: Permission denied
> >
> > when inittab tries to bring it up again.
> >
> > So, we have to kill the processes twice. And you have to wait a couple of
> > seconds before you kill them again, or it will have the same nssock
> > error.
> >
> > Thanks
> >
> > >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 privileged port on 4.0,
> > so I
> > >didn't notice this bug, which I now think it is.
> > >
> > >To recap:
> > >starting the server as root on a port <1024 defined in nsd.tcl,
> > switching
> > >to an unprivileged user "nsd" with -u:
> > >[02/Dec/2003:13:24:44][26609.3209707648][-main-] Error: nssock:
> > failed to
> > >listen on 127.0.0.1:81: Permission denied
> > >
> > >Starting as root with the same command line, but adding "-b
> > 127.0.0.1:81",
> > >server starts fine.
> > >
> > >Starting the server on a port >1024 defined in the config file works
> > fine
> > >as well.
> > >
> > >Another bug(?): when I send the server a normal kill (TERM), it comes so
> > >far as:
> > >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: nsmain:
> > >AOLserver/4.0 stopping
> > >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: stopping
> > >server: server1
> > >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv:
> > connection
> > >threads stopped
> > >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: driver:
> > shutdown
> > >complete
> > >
> > >But doesn't actualy exit. I need to send it another TERM to make it
> > exit.
> > >
> > >This is all running on "Linux wombat 2.4.22-1.2088.nptl #1 Thu Oct 9
> > >20:39:56 EDT 2003 i686 athlon i386 GNU/Linux" which is the Fedora final
> > >beta distribution. ("Severn")
> > >
> > >Bas.
> > >
> > >
> > >--
> > >AOLserver - http://www.aolserver.com/
> > >
> > >To Remove yourself from this list, simply send an email to
> > <[EMAIL PROTECTED]> with the
> > >body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> > Subject: field of your email blank.
> >
> >
> > --
> > AOLserver - http://www.aolserver.com/
> >
> > To Remove yourself from this list, simply send an email to
> > <[EMAIL PROTECTED]> with the
> > body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> > Subject: field of your email blank.
> >
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
> field of your email blank.
>
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] bind / privileged port
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.
>
> Relatedly, it is difficult to restart aolserver, because aolserver
> seems to
> hang on to port 80.
>
> We have aolserver in the inittab with
>
> /usr/local/aolserver4/bin/nsd -it /usr/local/aolserver4/nsd.tcl -u
> nsadmin
> -b 209.133.111.72:80
>
> But when it hangs (which is often), we can't just kill all the processes,
> because when we do, we always get:
>
> [02/Dec/2003:15:28:22][21164.1024][-main-] Error: nssock: failed to
> listen
> on 209.133.111.72:80: Permission denied
>
> when inittab tries to bring it up again.
>
> So, we have to kill the processes twice. And you have to wait a couple of
> seconds before you kill them again, or it will have the same nssock
> error.
>
> Thanks
>
> >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 privileged port on 4.0,
> so I
> >didn't notice this bug, which I now think it is.
> >
> >To recap:
> >starting the server as root on a port <1024 defined in nsd.tcl,
> switching
> >to an unprivileged user "nsd" with -u:
> >[02/Dec/2003:13:24:44][26609.3209707648][-main-] Error: nssock:
> failed to
> >listen on 127.0.0.1:81: Permission denied
> >
> >Starting as root with the same command line, but adding "-b
> 127.0.0.1:81",
> >server starts fine.
> >
> >Starting the server on a port >1024 defined in the config file works
> fine
> >as well.
> >
> >Another bug(?): when I send the server a normal kill (TERM), it comes so
> >far as:
> >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: nsmain:
> >AOLserver/4.0 stopping
> >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: stopping
> >server: server1
> >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv:
> connection
> >threads stopped
> >[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: driver:
> shutdown
> >complete
> >
> >But doesn't actualy exit. I need to send it another TERM to make it
> exit.
> >
> >This is all running on "Linux wombat 2.4.22-1.2088.nptl #1 Thu Oct 9
> >20:39:56 EDT 2003 i686 athlon i386 GNU/Linux" which is the Fedora final
> >beta distribution. ("Severn")
> >
> >Bas.
> >
> >
> >--
> >AOLserver - http://www.aolserver.com/
> >
> >To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the
> >body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to
> <[EMAIL PROTECTED]> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the
> Subject: field of your email blank.
>
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] bind / privileged port
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 have aolserver in the inittab with
/usr/local/aolserver4/bin/nsd -it /usr/local/aolserver4/nsd.tcl -u nsadmin
-b 209.133.111.72:80
But when it hangs (which is often), we can't just kill all the processes,
because when we do, we always get:
[02/Dec/2003:15:28:22][21164.1024][-main-] Error: nssock: failed to listen
on 209.133.111.72:80: Permission denied
when inittab tries to bring it up again.
So, we have to kill the processes twice. And you have to wait a couple of
seconds before you kill them again, or it will have the same nssock error.
Thanks
>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 privileged port on 4.0, so I
>didn't notice this bug, which I now think it is.
>
>To recap:
>starting the server as root on a port <1024 defined in nsd.tcl, switching
>to an unprivileged user "nsd" with -u:
>[02/Dec/2003:13:24:44][26609.3209707648][-main-] Error: nssock: failed to
>listen on 127.0.0.1:81: Permission denied
>
>Starting as root with the same command line, but adding "-b 127.0.0.1:81",
>server starts fine.
>
>Starting the server on a port >1024 defined in the config file works fine
>as well.
>
>Another bug(?): when I send the server a normal kill (TERM), it comes so
>far as:
>[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: nsmain:
>AOLserver/4.0 stopping
>[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: stopping
>server: server1
>[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: connection
>threads stopped
>[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: driver: shutdown
>complete
>
>But doesn't actualy exit. I need to send it another TERM to make it exit.
>
>This is all running on "Linux wombat 2.4.22-1.2088.nptl #1 Thu Oct 9
>20:39:56 EDT 2003 i686 athlon i386 GNU/Linux" which is the Fedora final
>beta distribution. ("Severn")
>
>Bas.
>
>
>--
>AOLserver - http://www.aolserver.com/
>
>To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
>body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] bind / privileged port
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 privileged port on 4.0, so I
didn't notice this bug, which I now think it is.
To recap:
starting the server as root on a port <1024 defined in nsd.tcl, switching
to an unprivileged user "nsd" with -u:
[02/Dec/2003:13:24:44][26609.3209707648][-main-] Error: nssock: failed to
listen on 127.0.0.1:81: Permission denied
Starting as root with the same command line, but adding "-b 127.0.0.1:81",
server starts fine.
Starting the server on a port >1024 defined in the config file works fine
as well.
Another bug(?): when I send the server a normal kill (TERM), it comes so
far as:
[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: nsmain:
AOLserver/4.0 stopping
[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: stopping
server: server1
[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: serv: connection
threads stopped
[02/Dec/2003:13:35:48][26689.3209711744][-main-] Notice: driver: shutdown
complete
But doesn't actualy exit. I need to send it another TERM to make it exit.
This is all running on "Linux wombat 2.4.22-1.2088.nptl #1 Thu Oct 9
20:39:56 EDT 2003 i686 athlon i386 GNU/Linux" which is the Fedora final
beta distribution. ("Severn")
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
Re: [AOLSERVER] bind / privileged port
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 start it? When I start it that way, it works: bin/nsd -t nsd.tcl -b 111.111.111.111:80 -g www -u www If I omit -b option, I get: [30/Nov/2003:19:09:45][30678.134533120][-main-] Error: nssock: failed to listen on 111.111.111.111:80: Permission denied 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). Artur -- // WWW: artur.black.pl // PGP: finger [EMAIL PROTECTED] // -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 message you get from AOLserver when you try to start it? Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 -- // WWW: artur.black.pl // PGP: finger [EMAIL PROTECTED] // -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 privilges to log/ and servers/server1/modules/nslog (or whatever your server is named) Not being able to bind to a port lower than 1024 as non-root user is not an AOLserver limitation, it is one set by the OS. Bas. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
Andrew, Mark. Thanks for the answers. Mark Page <[EMAIL PROTECTED]> writes: > There is a new command line argument which does this: >-b 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 set to equal values? Isn't it so, that -b is only required when I want AS4.0 to bind to the privileged port? Artur -- // WWW: artur.black.pl // PGP: finger [EMAIL PROTECTED] // -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
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 it what non-root user to become after it binds to the port. > Does AOLserver drop privileges before reading configuration file? I'm not sure exactly when AOLserver drops privileges and becomes the non-root user, but since you tell which port to bind to IN the config file, I guess AOLserver must still be root at that point. -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] bind / privileged port
There is a new command line argument which does this: -b 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 line? I couldn't find anything > about this in the documentation. > > Does AOLserver drop privileges before reading configuration file? > > Artur > > -- > // WWW: artur.black.pl // PGP: finger [EMAIL PROTECTED] // > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
