Was there a question in there? What version of AOLserver are you running? You might consider upgrading to the latest 3.5.x version, or go with the 4.0 beta if you don't need https.
In you run script, you might try adding a line like 'sleep 4', so that AOLserver doesn't restart too fast to grab the port. there is also a bind switch, on the command line add -b '192.168.1.1:80' or whatever your ip:port is.
If you don't like daemontools logging, don't use it! Remove your log directory and use regular AOLserver logging. Your run file command should change to something like 'nsd -it nsd.tcl'.
--Tom Jackson
Brady Wetherington wrote:
I use a daemontools setup, because I have problems with an nsd instance that ran itself out of memory and croaked. There are some caveats - at least with the version of AOLServer that I'm using -
#1) - Sometimes nsd will die but its threads will somehow still survive - very weird. Maybe this is due to the Linux version I'm using? I've found I have to eventually killall -9 the remaining threads. #2) - Often the time between the nsd dying and relaunching is too fast, and the new nsd is perfectly happy to launch without correctly snagging port 80. Also bad. I remember some talk about this very same issue a while ago, it's probably been fixed in some other version of aolserver.
However, I can hit svc -t aolserver and it will restart it for me. Which is nice.
All in all, I'm a bit disappointed with the setup. Additionally, I use the daemontools logging set up, and I don't like that very much either.
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
