On Tuesday 06 December 2011, Karl Eichwalder wrote:
Ludwig Nussel <ludwig.nussel(a)suse.de> writes:
Melchior FRANZ wrote:
Apparently, 12.1 has added /var/tmp/ to
/etc/sysconfig/cron. I was quite surprised when I found out today
that I've lost a few GB of data, which used to be safe there.
$ tail -2 /usr/lib/tmpfiles.d/tmp.conf
d /tmp 1777 root root 10d
d /var/tmp 1777 root root 30d
That tells systemd to clear files older than 10 resp 30 days in
those directories. systemd does not honor TMP_DIRS_TO_CLEAR.
I'm going to add this to the release notes:
Note that /usr/lib/tmpfiles.d/*.conf
contains systemd's default config only (should not be edited).
Users can change it in
but AFAIR this direcectory does not exist per default yet.
see man tmpfiles.d
The behavior per se is ok, but in the update case,
when it does not
honor old settings, I consider it as a bug. Are there plans to fix
And, of course, it would have been a bug, if default
and systemd related settings would differ...
If possible I would fix it in 12.1 by adding /etc/tmpfiles.d/*
which does nothing else than avoiding conflicts between
/etc/sysconfig/cron and /usr/lib/tmpfiles.d/*.conf.
Do we plan to remove
these variables from /etc/sysconfig/cron or will we propagate the
values from sysconfig to /usr/lib/tmpfiles.d/tmp.conf?
As said in 12.1 it has to be fixed.
In 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 only.
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org