On Thu, 27 Jan 2000 13:38:34 -0500 Bill Verity said:
>That was it.  At the start of listserv's log I found:
>
>        >>> LISTSERV already running on pid 107600 <<<
>        -> Clean shutdown of LISTSERV(107600) initiated...
>        -> LISTSERV(107600) successfully shut down.
>        >>> Cannot bind to local host, port 2306: error 67.
>
>Killing the two processes and restarting listserv solved the problem.  I guess
>once it can't bind that port it never tries again - right?

Right, it only tries when it starts up.

>The orphans were probably caused at our midnight restart.  I'm going to change
>that to 12:30 a.m. -- too much happening at 00:00.  Here is the log showing the
>kill problem:
>
>        >>> LISTSERV already running on pid 55698 <<<
>        -> Clean shutdown of LISTSERV(55698) initiated...
>        -> Timeout - attempting SIGKILL...
>        -> LISTSERV(55698) killed.
>
>We restart every six hours so the log files don't get too big.

How are you stopping it?  The only good ways to do this are to either
send a STOP command to LISTSERV or to do a 'kill -TERM' on the PID
of the parent process (you can cat the value in the listserv.PID file
found in the LSVSPOOL directory if you want).

If all you're doing is issuing a 'kill -9' or trying to simply issue
a 'go bg' command, you probably won't kill all of the children.

Nathan