Date: 19 Jan 1998 15:43:23 -0800 From: Christoph Toshok <toshok@Hungry.COM> To: freebsd-hackers@FreeBSD.ORG Subject: Re: user limits, login.conf, etc. Message-ID: <m2yb0c9gis.fsf@terror.hungry.com> In-Reply-To: jdp@polstra.com's message of 19 Jan 1998 12:29:36 -0800 References: <34C16A7A.9E950A3@netscape.com> <199801192025.MAA24381@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
jdp@polstra.com (John Polstra) writes: > > In article <34C16A7A.9E950A3@netscape.com>, > Chris Toshok <toshok@netscape.com> wrote: > > > Here's my login.conf entry: > > Not to insult your intelligence or anything, but did you run > "cap_mkdb /etc/login.conf" after you edited it? It's easy to > forget that step. > Yep, I've run cap_mkdb, and the problem remained. Here's the output of limits -a, taken after logging in from xdm and a virtual console. A shell from xdm: Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuse-cur 32768 kb memorylocked infinity kb maxprocesses-cur 64 openfiles 680 A Shell from a virtual console: Resource limits (current): cputime infinity secs filesize infinity kb datasize 524288 kb stacksize 65536 kb coredumpsize infinity kb memoryuse infinity kb memorylocked infinity kb maxprocesses 339 openfiles 680 There isn't a login class in /etc/login.conf that corresponds to either of them. Btw, I'm currently using bash-2.0. Not that I'd imagine it would make that much difference. The problem does go away (oh, I can *finally* run gdb) if I run 'limits -C root /usr/X11R6/bin/xdm' in /etc/rc.local. After I do that, the limits for xdm become the same as what I've listed for virtual consoles. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2yb0c9gis.fsf>