I know this has been discussed a lot but it's still showing up for me on occasion, especially with 3rd party non-LSB init scripts.
My suggestion would be to prioritise the jobs that we delete... can we tell that a job relates to a unit? And if so can we tell if a unit is sysv, lsb or native? If so I'd propose that when a job needs ot be deleted, we try to find a sysv job first, then an lsb then a native. That way we shouldn't end up with a sucky 3rd party sysv script killing prefdm startup as seems to be happening here: https://bugs.mageia.org/show_bug.cgi?id=5262#c36 Would that be feasible? Or do you think it's not even worth it (medium term goal is probably to disable support for non-native units at compile time anyway I guess...) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/ _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
