On Monday 01 January 2007 07:19 pm, Axel Thimm wrote:
> greylistd probably started, but the initfile didn't properly detect
> it, e.g. it is a cosmetical bug. Does the following patch to the init
> file fix this?
>
> # daemon --user greylistd /usr/sbin/greylistd
> initlog $INITLOG_ARGS -c "su -s /bin/bash - greylistd -c
> \"/usr/sbin/greylistd > /dev/null 2>&1 &\"" sleep 2
> - ps uax | grep -v grep | grep '/usr/bin/python
> /usr/sbin/greylistd' > /dev/null + ps uax | grep -v grep | grep
> '/usr/sbin/greylistd' > /dev/null RETVAL=$?
>
> base=greylistd
When I make this change I do get "OK" rather than "FAILED" but ...
is this what I want?
<snip>
$ ps wwwaux| grep greylistd
105 11993 7.1 0.7 10984 3920 pts/0 S 12:09
0:00 /usr/bin/python2.3 /usr/sbin/greylistd
root 12001 0.0 0.1 4612 648 pts/0 S+ 12:09 0:00 grep
greylistd
$
I thought I'd want to see greylistd running, not being called by a
running version of python. If this is correct then I'm seriously
confused as to how the daemon runs. But that's okay.
So you're saying this is correct?
Thanks.
Jeff
--
Jeff Lasman, Nobaloney Internet Services
1254 So Waterman Ave., Suite 50, San Bernardino, CA 92408
Our blists address used on lists is for list email only
Phone +1 909 266-9209, or see: "
http://www.nobaloney.net/contactus.html"
