On Tue, Dec 18, 2012 at 01:55:55PM -0800, Steve Langasek wrote:
> On Tue, Dec 18, 2012 at 09:43:38PM +0000, Roger Leigh wrote:
> > [sorry for delayed reply; I've been ill with flu since Sunday, and
> > I'm just catching up]
>
> > On Sun, Dec 16, 2012 at 08:42:54AM -0800, Steve Langasek wrote:
> > > On Sat, Dec 15, 2012 at 10:08:19PM +0000, Roger Leigh wrote:
> > > > Debian does clean /tmp at boot, though the FHS does recommend it.
> > > > And there's nothing to stop us adding the following to post_mountall:
>
> > > > rm -rf /tmp/user
> > > > mkdir -m 0755 /tmp/user
>
> > > > This gives us everything that /run/user gives us, without needing to
> > > > touch /run. Note that the primary motivation for it being under
> > > > /run AFAICT is that Fedora has pathological /tmp reaping behaviour
> > > > enabled by default, so this is a workaround for their brokenness
> > > > rather than there being an inherent need for it to be under /run.
>
> > > These same tmp reaping tools exist in Debian, and we have no control over
> > > whether admins are using them. It's not sufficient to use a directory
> > > which
> > > *on a default system* provides the required behavior.
>
> > > The FHS definition of /tmp does *not* allow it to fulfill the XDG's
> > > requirements.
>
> > We can certainly patch our tmpreaper and any alternatives to whitelist
> > the directory. This is not an insurmountable obstacle.
>
> Yes, it is. You're proposing to *change the semantics* of a directory
> that's part of a *standard*. Admins are allowed to rely on the behavior of
> this directory and run their *own* tmpreapers that we have no control over.
This is exactly the situation we have today, though. /tmp is used for
control sockets, pipes, etc., and we *do* whitelist them. This is the
list tmpreaper uses:
--protect '/tmp/.X*-{lock,unix,unix/*}' \
--protect '/tmp/.ICE-{unix,unix/*}' \
--protect '/tmp/.iroha_{unix,unix/*}' \
--protect '/tmp/.ki2-{unix,unix/*}' \
--protect '/tmp/lost+found' \
--protect '/tmp/journal.dat' \
--protect '/tmp/quota.{user,group}' \
We can just add /tmp/user to the list.
Now, if an end user uses a non-packaged tmpreaper then the
responsibility lies with them not to clean "important" stuff, and
there's already a wide and changeable range of stuff which meets
this category. I'm not sure that I consider the content of
/run/user to be so extra-special it can't fit in here.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
