3 ms·
I was having udev starting a separate ripping script as a background process, and it worked on pre-systemd udev systems. systemd kills the entire udev process
by zdw 9y ago
I was having udev starting a separate ripping script as a background process, and it worked on pre-systemd udev systems.
systemd kills the entire udev process tree (all children) including the ripping script after 30 seconds.
- inopinatus 9y agoTo fix this, perhaps it'll need to fork and detach the session, as per the standard daemonisation sequence. c.f. http://www.itp.uzh.ch/~dpotter/howto/daemonize http://www.itp.uzh.ch/~dpotter/howto/daemonize
- mst 9y agosystemd's session killing stuff will happily kill anything that's been daemonised by the standard approach :(
- JdeBP 9y agoActually, it's udevd itself doing that. A regular child-killing rampage is built into its main loop. To avoid it, one must arrange to not run the desired program directly, but rather to make udevd activate another service that in turn runs the desired program.