The MPD daemon is supposed to run at startup, but doesn't. It works fine when run normally (e.g sudo /etc/init.d/mpd start). I can't see any error messages either. I added some extra log_daemon_msg messages and rebooted, and can't still see the messages I added in log files at /var/log.

Where does this output go? How do I debug this?

The rc2.d links seem fine to me:

$ ls -ltra | grep mpd
lrwxrwxrwx 1 root root 13 2009-08-10 16:58 S30mpd -> ../init.d/mpd
lrwxrwxrwx 1 root root 21 2009-08-12 23:57 S20mpdscribble -> ../init.d/mpdscribble

What distribution and version?

Should mpdscribble not start after mpd?

Ah that might be it. Both mpdscribble and mpd were installed via packages so I trusted it to do the right thing. Off to give your suggestion a go ...

Try looking in /var/log/message or /var/log/dmesg

or you can try and see if any output shows up there. But I don't think it will.

Moving priorities around did not help. I've checked /var/log/* files - no error messages there. Since the start that's had error messages from mpdscribble (the binary, not the script) about mpd not running, but none from mpd itself.

I was wondering if it had anything to do with the fact that I changed the mpd script to point to my locally built version of /usr/local/bin/mpd. I can't see why /usr/local/bin would be unavailable at startup, but does anyone know if that's an issue ?

Btw, I'm on Ubuntu Jaunty, and trying to run an mpd version I built on this machine ( mpd-0.15.1 with mp3 streaming support )