On Tue, Dec 6, 2011, at 03:43 PM, Ruediger Meier wrote:
On Tuesday 06 December 2011, Karl Eichwalder wrote:
Ruediger Meier <sweet_f_a(a)gmx.de> writes:
Factory I would simply drop the idea of having interchangable
sysvinit and systemd. Users should know that using systemd or
sysvinit results in completely different behavior.
By considering this statement packagers could use systemd features
without thinking about sysvinit. Playing around systemd should IMO
not affect sysvinit and vice versa.
For this particular case it would mean that using systemd should
use /etc/tmpfiles.d/*.conf and sysvinit uses /etc/sysconfig/cron
Yes, but this would not save us from re-writing the docs on the
variables in /etc/sysconfig/cron. The statements there are just too
broad. At least, we must add warnings that sysconfig settings are
not valid for systemd.
My idea is to have really distinct systemd and sysvinit installations.
If you have systemd installed then there would be only /etc/tmpfiles.d/*
and no more /etc/sysconfig/cron and vice versa.
Hold on, cron isn't dead yet :) /etc/sysconfig/cron controls other
aspects of cron's functionality too. It may be one day that systemd
expands to encompass all of cron's functionalities but until then I
think the better solution is to properly mark the settings in
/etc/sysconfig/cron which are deprecated by systemd, and point the user
to the correct file(s) where the equivalent systemd settings are (or
proper documentation describing how to do it).
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org