Dave Mielke <d...@mielke.cc> writes: > [quoted lines by Samuel Thibault on 2016/06/29 at 13:50 +0200] > >>I believe that it's on purpose that udev kills the cgroup, and you are >>not supposed to escape from it. AIUI, you need to determine how to tell >>udev that the start was successful, and thus it shouldn't try to clean >>after start failure. > > I don't see any reference for how to do that. From the description for RUN > within my udev's man page: > > Starting daemons or other long running processes is not appropriate > for udev; the forked processes, detached or not, will be > unconditionally killed after the event handling has finished. > > This reminds me of the same kind of "we know best" thinking that the Pulse > Audio people display when it comes to making sounds from root. :-( I bet they > want to force everyone onto Systemd.
Yes, they do. As far as I know, long running processes via udev can now only be started by the SYSTEMD_WANTS thing. I guess the old udev behaviour is only working on old systems. Remember, these days, udev is part of systemd. -- CYa, ⡍⠁⠗⠊⠕ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
