On Wed, 22.04.15 17:59, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote:
> > So, I can see that having watchdog support during the activating phase > > might make sense in this case, but I am not sure this case is strong > > enough to add it to systemd proper, since it would complicate things > > for most: it's not a behaviour we can just enable for everybody, it > > would have to be something we'd have to add an explicit opt-in option > > for, since most daemons don't work like this. > > Thx for getting back to this again. > > An a bit more light weight variant could be adding a second watchdog > timeout parameter meant for the activation phase only. This timeout > value could be 0 (infinite) by default. This way, the feature is > probably invisible for all who are not explicitly setting it. Well, if it's a boolean or a timeout that is configured, I'd prefer not to add either option unless this turns out to be a frequently requested feature... I am just careful with adding even more settings so easily... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
