On Mon, Feb 07, 2005 at 07:20:09PM +0100, Tore Anderson wrote: > > Package: multipath-tools > Severity: normal > > From the Debian changelog: > > * Use start-stop-daemon to control the multipathd daemon and do it's own > PID file handling (which is now commented out of the daemon itself) > > This is broken, as you do not use the --pidfile nor the --make-pidfile > options of start-stop-daemon. Why do you want this behaviour anyway? > The normal way of doing it is to let the daemon itself create the pid > file, and let start-stop-daemon know about it with the --pidfile > option. --make-pidfile isn't always reliable either - see the comments > in start-stop-daemon's manual page. > > Putting the pidfile handling back into multipathd seemed to work just > fine for me, and kept the multipath binary from complaining about not > being able to signal multipathd. >
multipathd is started very early on in the boot process. often before /var is mounted. PID files go in /var/run and if that dir doesn't exist the PID file handling is even more (and dangerously so) broken. Granted, the current situation isn't great but at least it allows multipathd to actually start on systems where /var is on a seperate partition to root - which was not the case previously. -- patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
