On Sat, Jan 06, 2007 at 05:11:40PM +0100, Dr. Markus Waldeck wrote: > I compared the limits depending on the login method > (unlimited values removed).
> direct login: > -s: stack size (kbytes) 8192 > -c: core file size (blocks) 0 > -n: file descriptors 1024 > -e: max nice 0 > -r: max rt priority 0 > su: > -s: stack size (kbytes) 8192 > -c: core file size (blocks) 0 > -n: file descriptors 64 > -e: max nice 0 > -r: max rt priority 0 > Only the file descriptor limit differs. > Why are the other values are identical? Each of the other values listed here has an explicit default set in pam_limits, because RLIM_INFINITY is not a sane default for any of them -- not for nice and rt priority because these values have a finite scale, not for core file size because we want core files disabled by default, and not for stack size because... well, for no reason that I can actually distinguish from the case of RLIMIT_NOFILES, hmm. Thanks, you make a fair case; if we're shadowing the kernel's default for RLIMIT_STACK already, there's no reason we shouldn't be willing to do the same for RLIMIT_NOFILES. :) I'll take this upstream for further discussion. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
