From owner-freebsd-hackers  Mon Jan 19 15:43:37 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA04553
          for hackers-outgoing; Mon, 19 Jan 1998 15:43:37 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from terror.hungry.com (toshok@terror.hungry.com [169.131.1.215])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04541
          for <freebsd-hackers@freebsd.org>; Mon, 19 Jan 1998 15:43:24 -0800 (PST)
          (envelope-from toshok@Hungry.COM)
Received: (from toshok@localhost)
	by terror.hungry.com (8.8.8/8.8.7) id PAA02274;
	Mon, 19 Jan 1998 15:43:23 -0800 (PST)
To: freebsd-hackers@FreeBSD.ORG
Subject: Re: user limits, login.conf, etc.
References: <34C16A7A.9E950A3@netscape.com>
	<199801192025.MAA24381@austin.polstra.com>
From: Christoph Toshok <toshok@Hungry.COM>
Date: 19 Jan 1998 15:43:23 -0800
In-Reply-To: jdp@polstra.com's message of 19 Jan 1998 12:29:36 -0800
Message-ID: <m2yb0c9gis.fsf@terror.hungry.com>
Lines: 53
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk

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