On Thu, 4 Oct 2018 21:58:38 +0200 Michael Biebl <bi...@debian.org> wrote:
> > 1) revert the 791944 patch, create a new init.d/udev-clear script to > > remove the control file and run it just after sendsigs (this will > > restore the old well tested behavior) > > The removal of the control file should be bound to the live time of > the udev service, so splitting it off into a separate init script is > not a good idea. yes, to be sure, we should call udev-clear before sendsigs this will mimic the old behavior, where the control file doesn't exists after sendsigs I think this is the first step we should do to restore the functionality, then we have more time to find the proper solution, but at least we will not miss another stable release without a functioning udev + sysvinit + dmsetup/cryptdisks > Afaics this problem is unfortunately not really fixable with the > limited facilities sysvinit/sysv-rc provides. this is why I think we should consider to live with a workaround, that at least allows the users to boot and shutdown the system > A proper solution might (emphasis on might, as I haven't checked this) > be to teach start-stop-daemon about daemons using the sd-notify > interface. This is a more elaborate fix, for sure, but everything else > feels like an incomplete hack. yes, probably this is a good solution as start-stop-daemon is called in parallel, it could be required to create a different notify socket per instance, but luckily the client library manage the NOTIFY_SOCKET environment variable another possible solution is to add an option to udev to remove the control file on exit, as it was in the past thank you and ciao!
