On Sat, Apr 11, 2015 at 7:21 PM, Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote:
> On Sat, Apr 11, 2015 at 02:26:57PM +0200, Kai Krakow wrote: > > dean <deanshann...@gmail.com> schrieb: > > > > > Ok thanks for your prompt reply. It is my understanding the the > > > house-keeping-plugin "cleans" /tmp so does it need access? > That sounds wrong. First, systemd is already cleaning /tmp, so nothing > good is going to come out of cleaning it twice. I think the difference here is that g-s-d has per-user configuration, so user A can set the expiry for their own files to 1 day, user B can set it to 7 days, and systemd can enforce a system-wide maximum of 10 days. Though it can be confusing if the GNOME UI allows selecting a longer expiry than systemd has. > If the user is not running, > the cleanup is not going to happen, so on a multi-user system, when the > user logs out, files would stay around infinetely. Well, tmpfiles.d enforces it anyway. > So cleanup from > the graphical session is ineffective. More importantly, an unprivileged > user cannot access files without bumping their access time stamp. So > trying to do the cleanup as an unprivileged user actually interferes > with systemd-tmpfiles (see df99a9ef5bb7a89b92 and > https://bugzilla.redhat.com/show_bug.cgi?id=1183684). > Even a stat()? Ouch. -- Mantas Mikulėnas <graw...@gmail.com>
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
