croft@su-aimvax.ARPA (04/16/86)
From: Bill Croft <croft@su-aimvax.ARPA> Since the news unbatcher has gone berzerk on us twice already, I offer this expedient for harried vax managers until Brian gives us a fix: just type: yourhost# killstring news And the shell file: ---- #!/bin/sh # # killstring string # # shell file to kill all processes owned by "string" or having # names containing "string". set -x kill -9 `ps aux | sed -e "/$1/!d /killstring/d s/^[a-z]* *\([0-9]*\) .*/\1/" `
croft@su-safe.ARPA (04/21/86)
From: Bill Croft <croft@su-safe.ARPA> Brian, what has happened on diablo (at least three times) is that the unbatcher (which is started by cron every 15 minutes) will sometimes never exit. Perhaps this is because it is reading a prematurely truncated batch file in /usr/spool/news (because of the rcp hangs?) Anyway with new incarnations showing up every 15 minutes, we have seen situations of almost a hundred unbatcher related processes (shells, su, unbatcher itself) just hanging around. Of course after a few dozen of them get going, the error log file fills up with messages that new 'news' processes can no longer fork. The kludgy shell file I sent out just lets me kill off all of these guys easily. After the next unbatcher starts up, things 'seem' to be better. I don't understand it, but I'd be glad to message or call you if it happens again. Everything's fine now...