kill -s 9 PID
where PID is the process ID
I thought it was kill -9 PID
I just tested kill -s 9 PID and it works.
If the doesn't work try the command on other processes, also check the kill command against a known good kill command on another system to make sure it hasn't been corrupted.
On Mandrake 9.1 kill and killall are in /usr/bin and are programs rather than scripts.
Jim K
Bob Crandell wrote:
Cory Petkovsek ([EMAIL PROTECTED]) wrote:
On Thu, Jun 05, 2003 at 02:21:17AM +0000, Bob Crandell wrote:
The problem will start again if I enable SPAMAssassin with /etc/procmailrc.
Procmail version is 3.15.2. It is the stock one.
I'm also using 3.15.2. Do you still have mail in a filter queue? I would tell procmail to start logging. Use the verbose option and a logfile so you can see what it thinks it is doing. In a spamassasign procmailrc or /etc/procmailrc put: LOGFILE=/var/log/procmail.log VERBOSE=yes
This is Slackware 8.1 with kernel 2.4.20-xfsPerhaps you got a really devious spam.
This server had been running almost 9 months before this cropped up.
Cory
_______________________________________________
I enabled SpamAssassin with VERBOSE=yes. Plus I installed the latest version of SpamAssassin. Seems I was a couple of versions behind. Before, it took 3 or 4 hours to make the system unusable. It's been running about 30 minutes now. It's time to watch and see.
Thanks
-- Bob Crandell Assured Computing When you need to be sure. [EMAIL PROTECTED] www.assuredcomp.com Voice - 541-689-9159 FAX - 541-463-1627 Eugene, Oregon
_______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug
_______________________________________________ EuG-LUG mailing list [EMAIL PROTECTED] http://mailman.efn.org/cgi-bin/listinfo/eug-lug