]] Roger Leigh | /run/user is created by systemd. This contains within it directories | owned by logged in users e.g. /run/user/rleigh in my case, and the | environment variable XDG_RUNTIME_DIR is set to this location.
This only happens if you use libpam-systemd, doesn't it? | There are a few problems with this: | | 1) Any user can now trivially DoS the system by filling up /run. | 2) The directory is a session-specific directory, and this only | permits one login session at once, at least if one wants to have | per-session state, rather than shared between sessions. Agreed on those counts, though if the admin is worried about the former, it's trivial to mount a size-constrained tmpfs on top /run/user. | 3) /tmp is already suitable for this purpose: systemd can use | /tmp/user in exactly the same way. /tmp is allowed to loose information more easily than /run, though. | While /tmp isn't necessarily a tmpfs like /run, please note that: | 1) /run isn't necessarily a tmpfs either | 2) /tmp can be made a tmpfs | 3) systemd can easily create an empty /tmp/user at startup; it can | even remove the directory tree if present from a previous boot | to ensure it's clean from the start. Or the admin can create a symlink from /run/user to /tmp/user and make sure the latter exists themselves. I'm not sure I'm going to do anything about this bug since I don't really agree with it being a bug to begin with and if an admin wants a different behaviour, that's easy enough to set up. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
