https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c1 Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Curt.Blank@curtronics.com --- Comment #1 from Robert Milasan 2012-12-03 11:59:35 UTC --- Whats the memory available on the system? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c3 --- Comment #3 from Curtis J Blank 2012-12-03 14:29:03 UTC --- Better yet, in addition to including a size= configurable parameter say if the memory is over 8G have boot set the maximum to 2G or 4G. See no reason for any of these tmpfs filesystems to be allocated with more then that amount. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c5 Curtis J Blank changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Curt.Blank@curtronics.com | --- Comment #5 from Curtis J Blank 2012-12-03 14:42:08 UTC --- I know it's the default I said that, that doesn't mean it's a good practice. Yes on a small system as you mentioned but not on a big system. And yes I'll set it to a more reasonable value but then you'll do an update and wipe it out. If it's a configurable value then chances are it will survive an update. Yes, it doesn't mean it will be used but it does mean that it *can* be used. With 1% normal usage 1G is plenty. Even 256M is plenty. If you have a system with 1G of memory you are setting it to 512M, like I said 256M is plenty so why not set it to 256M? Or 512M? Then you have your small systems covered and big systems are not set to an excessive value. I was going to knock it down to 25% on next boot but now I'm thinking maybe 256M or 512M. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c7 Curtis J Blank changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Curt.Blank@curtronics.com | --- Comment #7 from Curtis J Blank 2012-12-03 15:03:28 UTC --- /etc/init.d/boot & /etc/init.d/boot.localfs boot: mount -n -t devtmpfs -o mode=0755,size=25% devtmpfs /dev boot: mount -n -t tmpfs -o mode=0755,nodev,nosuid,size=25% tmpfs /run boot: mount -t tmpfs -o mode=1777,size=25% tmpfs /dev/shm boot.localfs: mount -fv -t tmpfs -o mode=1777,size=25% tmpfs /dev/shm boot.localfs: mount -n -t tmpfs -o mode=0755,nodev,nosuid,size=25% tmpfs /media But that doesn't cover /var/run, have to look for that one yet. But now I'll have to remember to check those every time you do an update and that is a PITA. You surely don't need a 16G filesystem for /media... And that's one of the dangers, somebody thinks they have something mounted there and don't so they mv vidoes there and guess what, you're using it... And on boot they're gone... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c9 --- Comment #9 from Robert Milasan 2012-12-03 18:57:03 UTC --- OK, for /media, you could change the options in /lib/systemd/system/media.mount, but the rest of them are hard-coded in systemd and without some patch wont work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.