Am 2015-12-02 15:04, schrieb Felipe Sateler:

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.

A 2way gateway you play then? :)

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

And thats why I love the BTS: Nice, central, mail controlled place. No need for users to deal with trillions of different upstream trackers.

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.

Yes they could. Unless, see below. :)

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.

/run is an extra tmpfs mount anyways.

In my case, /run/user is one too. Quite small, but besides systemd there is nothing using it anyways.

--
bye Joerg

Reply via email to