/etc/init.d/dmeventd should start before lvm (at least with baselayout2) in the boot runlevel, otherwise snapshotted volumes produce error messages when starting lvm.
Created attachment 170200 [details, diff] start /etc/init.d/dmeventd before /etc/init.d/lvm
Thanks for reporting this issue and submitting a fix :) Assigning to maintainers.
Created attachment 171445 [details, diff] remove pidfile option from /etc/init.d/dmeventd --pidfile is being ignored by /sbin/dmeventd because its a compile time option.. so it can be removed from the init script
Created attachment 171463 [details, diff] alternative pidfile (/root/dmeventd.pid instead of /var/run/dmeventd.pid) another problem i stumbled across: there is a problem stopping dmeventd when you start dmeventd in the boot runlevel and have /var on a different volume than / because the pidfile /var/run/dmeventd.pid isnt visible anymore. a solution for me is to use /root/dmeventd.pid as pidfile.. but thats probably not an ideal solution.. anyone got an idea?
Better approach would be to change the init script to let start-stop-daemon fork it and let s-s-d write the pidfile. Just use the -d option with dmeventd for this, that way we don't have to set the pidfile at compile time. Or, patch the code to take a pidfile option.
(In reply to comment #3) > Created an attachment (id=171445) [edit] > remove pidfile option from /etc/init.d/dmeventd > > > --pidfile is being ignored by /sbin/dmeventd because its a compile time > option.. so it can be removed from the init script > The --pidfile option is actually being passed to s-s-d, not dmeventd, however dmeventd is forking after the fact.
not using dmeventd works for me..
