Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

On Thu, 26.05.16 08:13, Francis Moreau (francis.m...@gmail.com) wrote: > On Wed, May 25, 2016 at 11:10 PM, Michael Biebl wrote: > > And if a service does not have an explicit stop on shutdown/reboot, > > the processes are killed in a final killing spree where there are not > >

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

2016-05-26 8:25 GMT+02:00 Francis Moreau : > Well yes that's not usefull, so I'm wondering why systemd has code to > deal with this weid case specially since by default all stubs will > have a Conflicts/Before=shutdown.target. The generator code is generic, there is no

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

On Thu, May 26, 2016 at 8:15 AM, Andrei Borzenkov wrote: > On Thu, May 26, 2016 at 8:49 AM, Francis Moreau > wrote: >> >> So let's take an example. Please note that I'm really not sure what's >> the expected behavior of sysvinit itself, and finding

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

2016-05-26 7:49 GMT+02:00 Francis Moreau : > Hello Michael, > > On Wed, May 25, 2016 at 11:08 PM, Michael Biebl wrote: >> Hm, I've already given you the answer on IRC, so I'm not sure why you >> ask them again. >> > > Indee and thank you for that. > > But

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

Hello Michael, On Wed, May 25, 2016 at 11:08 PM, Michael Biebl wrote: > Hm, I've already given you the answer on IRC, so I'm not sure why you > ask them again. > Indee and thank you for that. But you also told me that /etc/init.d/rc0.d isn't supported by Debian, and my

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

And if a service does not have an explicit stop on shutdown/reboot, the processes are killed in a final killing spree where there are not ordering guarantees. 2016-05-25 23:08 GMT+02:00 Michael Biebl : > Hm, I've already given you the answer on IRC, so I'm not sure why you >

Re: [systemd-devel] sysv-generator weirdness for shutdown runlevels

Hm, I've already given you the answer on IRC, so I'm not sure why you ask them again. The K symlinks determine whether a service needs an explicit stop request on shutdown (i.e. Conflicts/Before: shutdown.target). That's exactly how sysvinit also worked. If there was a K symlink in rc0 and rc6,

[systemd-devel] sysv-generator weirdness for shutdown runlevels

Hello, I'm starring at a chunk of code of the sysv-generator (shown below) for some while now and I still can't see its purpose. Here's the code taken from src/sysv-generator/sysv-generator.c: static int set_dependencies_from_rcnd(const LookupPaths *lp, Hashmap *all_services) { [...]