I can confirm this as I've seen this behavior since the earlier version that was in potato. I do however notice that it does actually stop the slurpd processes and that the messages are merely an annoyance of an unclean check... I don't believe the slurpd process itself creates a PID file and thus start-stop-daemon must use something along the lines of a 'pidof slurpd' call which will return multiple PIDs due to the threading issue...
Jeremy
On Wed, Mar 05, 2003 at 02:55:10PM +0200, Alexey Chetroi wrote:
>
> Dear All,
>
> I've configured slapd and slurpd on my woody box and everything
> works fine, except when I restart slapd, init script complains about
> missing pid of slurpd:
>
> lexa:/home# ps -ef|egrep 'slapd|slurpd'
> root 21418 1 0 13:37 ? 00:00:00 /usr/sbin/slapd
> root 21420 1 0 13:37 ? 00:00:00 /usr/sbin/slurpd -t /var/spool/slurpd
> root 21421 21418 0 13:37 ? 00:00:00 /usr/sbin/slapd
> root 21422 21420 0 13:37 ? 00:00:00 /usr/sbin/slurpd -t /var/spool/slurpd
> root 21423 21422 0 13:37 ? 00:00:00 /usr/sbin/slurpd -t /var/spool/slurpd
> root 21424 21421 0 13:37 ? 00:00:00 /usr/sbin/slapd
> root 21425 21422 0 13:37 ? 00:00:00 /usr/sbin/slurpd -t /var/spool/slurpd
> root 21477 17672 0 14:39 pts/0 00:00:00 egrep slapd|slurpd
> lexa:/home#
> lexa:/home# /etc/init.d/slapd restart
> Stopping OpenLDAP: slapd slurpdstart-stop-daemon: warning: failed to kill 21423: No
> such process
> start-stop-daemon: warning: failed to kill 21422: No such process
> start-stop-daemon: warning: failed to kill 21420: No such process
> .
> Starting OpenLDAP: slapd slurpd.
> lexa:/home#
>
> I think it kills 1st slurpd (which are threads actually?) start-stop-daemon
> tryes to kill other slurpds which are gone already. Just want to know if
> it is normal behavior.
>
> --
>
> Best regards,
> Alexey Chetroi
>
> ---
> Smile... Tomorrow will be worse. (c) Murphy's law
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
pgp00000.pgp
Description: PGP signature
