in my test server -K and TERM both work fine. here's what it says:
Notice: nsmain: AOLserver/3.3.1+ad13 stopping
Notice: nssock: triggering shutdown
Notice: serv: stopping connection threads
Notice: serv: connection threads stopped
Notice: sched: shutdown pending
Notice: sched: shutdown started
Notice: sched: shutdown complete
Notice: exiting
Notice: drv: driver 'nsunix' stopping
Notice: socks: shutdown pending
Notice: nscp: shutdown
Notice: socks: shutdown complete
Notice: at shutdown *** MY NOTICE
Notice: nslog: closing '/home/aolserver/log/sfr/sfr_access.log'
Notice: nssock: shutdown complete
Notice: nsmain: AOLserver/3.3.1+ad13 exiting
but on my production server I only get
Notice: nsmain: AOLserver/3.3.1+ad13 stopping
Notice: nssock: triggering shutdown
Notice: drv: driver 'nsunix' stopping
Notice: keepalive: shutdown pending
Notice: keepalive: shutdown complete
Notice: serv: stopping connection threads
The difference appears to be that my production server is starting a keepalive thread even though I have keepalivetimeout = 0 specified which is supposed to disable it. The test server ran off the same config file and did NOT start a keepalive thread. I noticed that Ns_ConnClose always calls NsKeepAlive on to-be-closed connections so figured maybe the difference was I never actually requested any pages from the test server. So I did that; no difference.
So now my second question, probably related to my first, is, how do I REALLY kill keepalive?
