Bug#806885: systemd: Unable to disable mount of /run/user/$something

[Felipe Sateler]

On 2 December 2015 at 10:20, Joerg Jaspert <joerg at debian.org> wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear Maintainer,
>
> (thats mostly a bug/feature for upstream, please forward to wherever needed,
> thanks).

In general, I'm not comfortable forwarding stuff that I won't
personally use, since if feedback is required then I would not now
what to respond.

Upstream tracker is at https://github.com/systemd/systemd/issues

>
> It seems that the mounting of /run/user/$something as tmpfs can not be
> disabled. Would be nice if it has an option for this.
>
> Background / Use case: We have a login server here, the only way to
> reach our internal machines.  This is pretty restricted, down to the
> inability of any new mount while the system is running. Yet, logind
> does try to mount the /run/user/$id on every users login (well, inital
> session creation), which gets denied.
>
> As the directory gets created before the mount (and thankfully chmod
> 700 too), there is no trouble - it is there for whatever wants to use
> it (nothing, really), but every mount try spits out an error.

Note, however, that without the per-user tmpfs, any user can exhaust
the system-wide runtime
space. So you might want to reconsider if mount failure is innocuous.

>
> An option to turn off this behaviour would be nice.

I don't think upstream will like this, due to the above. A single
tmpfs mount for all users might be an acceptable alternative.


-- 

Saludos,
Felipe Sateler