Matthew.van.Eerde wrote:
There seems to be a problem with clamav-milter's --pidfile option.
I retract this. The --pidfile option is fine.
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an
On Sep 24, 2004, at 13:48, [EMAIL PROTECTED] wrote:
Matthew.van.Eerde wrote:
There seems to be a problem with clamav-milter's --pidfile option.
I retract this. The --pidfile option is fine.
Line 1408 of clamav-milter.c has
fprintf(fd, %d\n, (int)getpid());
which
Doug Hardie wrote:
On Sep 24, 2004, at 13:48, [EMAIL PROTECTED] wrote:
Matthew.van.Eerde wrote:
There seems to be a problem with clamav-milter's --pidfile option.
I retract this. The --pidfile option is fine.
Line 1408 of clamav-milter.c has
On Sep 24, 2004, at 16:30, [EMAIL PROTECTED] wrote:
Doug Hardie wrote:
On Sep 24, 2004, at 13:48, [EMAIL PROTECTED] wrote:
Matthew.van.Eerde wrote:
There seems to be a problem with clamav-milter's --pidfile option.
I retract this. The --pidfile option is fine.
Line 1408 of clamav-milter.c has
On Fri, 2004-09-24 at 18:30, [EMAIL PROTECTED] wrote:
Yes but I retract my opinion that this is a problem. kill `cat clamav-milter.pid`
wasn't working, and I wrongly blamed this on the newline.
It turned out after experiment that kill $PID wasn't working either.
But killall clamav-milter
There seems to be a problem with clamav-milter's --pidfile option.
It successfully writes the PID to the file but then it also puts a trailing newline.
This makes it unsuitable for the standard
kill `cat /the/pidfile`
trick.
As a workaround this seems to work:
kill `head --bytes=-1
