On Tue, Dec 18, 2012 at 11:29:20PM +0100, Michael Biebl wrote: > > Additionally, the size limit of 100M is far to large, by about two > > orders of magnitude. This is a directory for storing service
> This size is taken from what mountall/upstart uses. Imho it makes sense > to use something that is consistent across different init systems. > If we are to talk about a different default size for /run/user, this > should be changed for mountall, too, so I've CCed Steve. Well, I don't think there's any value here that will make everyone happy. But AIUI, the memory isn't used unless files are actually allocated, so the only cost to having an oversized tmpfs is that a user can DoS the system by filling it up and depriving processes of needed memory. Also, it's not correct that the directory is used only for service sockets and pipes. Dconf, for instance, uses it for writing out cache files. These files will normally be small, but on a massively multiuser system, it's not inconceivable that the 1MB limit you proposed would be exceeded. On my own system, I have 52K used on /run/user; so 100MB allows < 2000 simultaneous logins. I'm happy to tune the exact value based on concrete feedback that it's causing problems for users on low-mem systems. The value used here was arrived at based on public discussion at UDS about the tradeoffs; session notes are here for reference: https://blueprints.launchpad.net/ubuntu/+spec/foundations-q-xdg-runtime-dir -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
