Hi Christoph,
> Still seeing, th pid file appears to be correct
>
> christoph@mitoraj {1} ~
> 10:23 0 % ps aux | grep 2200
> 1000 7219 0.0 0.0 9108 1564 ? S+ 10:23 0:00 grep 2200
> mpd 2200 0.0 0.1 233332 11240 ? Ss 10:05 0:00 /usr/bin/mpd
> /etc/mpd.conf
> christoph@mitoraj {1} ~
> 10:23 0 % cat /run/mpd/pid
> 2200
> christoph@mitoraj {1} ~
> 10:23 0 % sudo service mpd stop
> [ ok ] Stopping Music Player Daemon: mpd.
> christoph@mitoraj {1} ~
> 10:24 0 % ps aux | grep 2200
> 1000 7344 0.0 0.0 9108 1564 ? S+ 10:24 0:00 grep 2200
> mpd 2200 0.0 0.1 233332 11240 ? Ss 10:05 0:00 /usr/bin/mpd
> /etc/mpd.conf
could you debug this a little more please?
E.g. run 'sudo bash -x /etc/init.d/mpd stop' again. If that contains the
correct call to start-stop-daemon, like
+ start-stop-daemon --stop --quiet --oknodo --retry 5 --pidfile /run/mpd/pid
--exec /usr/bin/mpd
+ log_end_msg 0
then both initscript and pitfile are correct and I have no idea what
start-stop-daemon thinks it's doing...
Any other ideas what may be special in your case? And I suppose you've
upgraded from 0.16.8-1 to 0.17.4-3 in the meantime?
Florian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
