FS#27597 - spamassassin's spamd daemon fails to stop

Attached to Project: Arch Linux
Opened by Kyle Kaminski (nfm) - Friday, 16 December 2011, 18:58 GMT
Last edited by Florian Pritz (bluewind) - Monday, 16 January 2012, 08:57 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I'm having an issue where spamd daemon fails to stop. Looking at /etc/rc.d/spamd, I added a simple echo ${PID } statement to print the result of:
PID=`pidof -o %PPID /usr/bin/vendor_perl/spamd`

but for me it always comes out empty. So could this be the problem?
This task depends upon

Closed by  Florian Pritz (bluewind)
Monday, 16 January 2012, 08:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  spamassassin 3.3.2-3
Comment by Jay Williams (ice9) - Sunday, 01 January 2012, 06:26 GMT
Yes, pidof is failing to find the PID of the process, because pidof is apparently looking for an EXACT match, including options. I changed the line to:

PID=`pidof -o %PPID "/usr/bin/vendor_perl/spamd -d ${SPAMD_OPTS}"`

and it works for me now. I don't like it much, but I could not find a way to do an inexact match with pidof.

A commenter from an earlier bug report suggested something like this:

PID=`pgrep -f '^/usr/bin/vendor_perl/spamd'`

which also works.
Comment by Kyle Kaminski (nfm) - Thursday, 05 January 2012, 00:59 GMT
Hello,
Thanks for replying. I can confirm that:
PID=`pgrep -f '^/usr/bin/vendor_perl/spamd'`

works pretty well. I also found the previous bug report  FS#25043 , sorry for the duplicate!
Now I wonder why hasn't been this fixed yet? Hello? It's only a one-liner :).

Loading...