Hrm. There's no parent in that output.
Try "ps -ef | grep spamd" and see what happens.
not sure what you're looking for here, but,
% ps -ef | grep spamd
ps: illegal option -- f
> kills the two child processes, which then immediately restart.
Yeah, you need to deal with the parent, not the children.
hm.
if i replace,
--allowed-ips=192.168.1.10,127.0.0.1 --listen-ip=127.0.0.1 --port=783
with,
--socketpath /var/proc/spamd.sock --socketowner spamassassin
--socketgroup spamassassin --socketmode 0664
and then relaunch spamd,
checking, i see, now,
ps -ax | grep -i spamd
24190 ?? Ss 0:11.55 /usr/bin/perl -T -w
/usr/local/spamassassin/bin/spamd ... --allow-tell --daemonize
--min-children
24213 ?? S 0:00.07 spamd child
24214 ?? S 0:00.07 spamd child
24216 p2 S+ 0:00.00 grep -i spamd
so the master is here now.
this 'missing master' is, for me, reproducible when spamd is launched
using TCP sockets.
anyway, now, with spamd launch on UNIX sock,
kill `ps -ax | grep \? | grep "bin/spamd" | cut -c1-5`
works as expected.
as i use spamd on localhost to my MTA, UNIX sock is just fine.
are there any DISadvantages to launching spamd on a UNIX socket, vs a
TCP socket?
