On 02/17/2013 07:28 PM, Philip Guenther wrote:
Okay, so the openfiles settings was completely overridden (for class
staff) by the openfiles-max and openfiles-cur settings...but the -cur
value was 1024 too.  So, you _should_ be seeing a value of 1024.
Indeed, if I copy your exact 'staff' and 'default' classes into my
system's login.conf and then login on another virtual terminal, I get
1024.

I will concur that (in this login.conf) the *default* user class openfiles setting would be overridden by the *staff* user class settings. (e.g., if the default class openfiles were reduced to 512 in login.conf, a staff class user should still have an openfiles soft limit of 1024).

So, the next questions are things like "do you have ulimit lines in
any (whether system or per-user) of your shell startup files?"  "How
_exactly_ are you logging in: console virtual terminal, xdm, ssh,
other?"

Awesome sanity check! That is exactly the problem. I snagged a .kshrc file from another system on which I tinkering with [go][1]. Some ulimit settings (described in this [wiki][2]) were hastily placed in that kshrc. They slipped past my attention when I cannibalized the file for my new box. I fixed the kshrc and everything works as expected. Thanks for your help!

[1]: http://golang.org/
[2]: http://code.google.com/p/go-wiki/wiki/OpenBSD

Reply via email to