Re: Default size limits for /run (/var/run) and /run/lock (/var/lock)
I'm reading (can't spend allot of time though, I'll try)
I'm thinking (I'm not sure) that Bastien is working on this. He'd
mentioned issues between sysinit and running on certain vservers.
While reading scripts it reminded me, /etc/default, I have an older bug
/ comment to mention! There shouldn't be any "magic" in /etc/default.
It's a bad practice to have magic in /etc/default. Any magic an init
script needs to remain right in the init script itself. Why?
1) so the two are never separated
2) so a lack of "defaults" doesn't ammount to broken initscript
3) so if I use MY init script, or an older one, it is not foo'd
thanks I hope that helps anyone :)
Bastien ROUCARIES wrote:
On Thu, Apr 14, 2011 at 4:20 AM, Karl Goetz <email@example.com> wrote:
On Wed, 13 Apr 2011 10:32:42 +0100
Roger Leigh <firstname.lastname@example.org> wrote:
On Tue, Apr 12, 2011 at 12:38:03PM +0100, Roger Leigh wrote:
Following the discussion yesterday, I'd like to propose doing
something like the example below. It's possible to size a tmpfs
as a percentage of core memory, the default being -o size=50%.
Rather than setting an absolute value, we can size e.g. /run
as a percentage of total memory, which should scale with /run
usage better than a fixed value.
/run/shm: No default (use general tmpfs default of 20%)
/tmp: No default (use general tmpfs default of 20%)
20% doesn't seem like a lot for /tmp when people try and compile
something. While its not something most people end up doing, it does
seem odd to make people change their tempfs size before they can start
building packages for debian/themselves.
just a thought,
And moreover for scientific computation /tmp need to be on an
harddisk. I do not want my 16GiB matric to go to memory when I have
only 8GiB of RAM....
Please do not put /tmp on tmpfs use a bind mount of a rw partition
Karl Goetz, (Kamping_Kaiser / VK5FOSS)
Debian contributor / gNewSense Maintainer
No, I won't join your social networking group