I have installed sys-fs/multipath-tools 0.4.7 and I have found an error in the init.d script. In /etc/init.d/multipathd file is path /usr/sbin/multipathd and it should be /sbin/multipathd. Also, when I try to stop already started multipathd daemon, it do not stop it and I have to kill it manualy.
One more thing is not correct. If I add alias into the multipath.conf, it do not create the /dev/mapper/alias_name. I think it is because of the udev configuration.
fixed in 0.4.7-r1, thanks for the report !
(In reply to comment #2) > fixed in 0.4.7-r1, thanks for the report ! It still doesn't create the alias. In "man devmap_name" is mentioned something else then what is in /etc/udev/rules.d/40-multipath.rules: KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", \ NAME="%k", SYMLINK="%c" It would be nice to have alias instead of the bloody mplath device name.
(In reply to comment #3) > (In reply to comment #2) > > fixed in 0.4.7-r1, thanks for the report ! > > It still doesn't create the alias. OK, it was my fault. I had badly defined device in multipath.conf. But it still doesn't stops multipathd if I use the "/etc/init.d/multipathd stop". I solved that if I changed the stop command to this one: start-stop-daemon --stop --quiet --exec /sbin/multipathd I have triend to add --retry 5 to KILL the process after 5 secs but it didn't worked for me. Could you change it in the ebuild? Thanks.
works fine for me
(In reply to comment #5) > works fine for me What works for you? My solition or current solution what is in the ebuild now? What HW do you have?
using start/stop works for me ... i dont actually use device mapper
OK, I vote for to replace old stop line in the init.d script with this one: start-stop-daemon --stop --quiet --exec /sbin/multipathd
no ... it produces a pid file so we're going to use it
(In reply to comment #9) > no ... it produces a pid file so we're going to use it But if the pid way doesn't work properly, then you sould switch to the exec way. You sould search way how it works for everybody and not only for somebody!
except that it does you're probably experiencing a bug that we've fixed elsewhere in the meantime, change --pid to --pidfile in your local copy
(In reply to comment #11) > except that it does > > you're probably experiencing a bug that we've fixed elsewhere > > in the meantime, change --pid to --pidfile in your local copy > Thank you. With "--pidfile" instead of the "--pid" it works very well. Would be possible to change it in a portage?
