From emoore@thrush.sover.net  Thu Jan  8 13:58:38 1998
Received: from thrush.sover.net (freeman.sover.net [204.71.16.52])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA06023
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 8 Jan 1998 13:58:36 -0800 (PST)
          (envelope-from emoore@thrush.sover.net)
Received: (from emoore@localhost)
	by thrush.sover.net (8.8.7/8.8.7) id QAA01789;
	Thu, 8 Jan 1998 16:58:28 -0500 (EST)
	(envelope-from emoore)
Message-Id: <199801082158.QAA01789@thrush.sover.net>
Date: Thu, 8 Jan 1998 16:58:28 -0500 (EST)
From: Evan R Moore <emoore@thrush.sover.net>
Reply-To: emoore@sover.net
To: FreeBSD-gnats-submit@freebsd.org
Subject: Trouble setting resource limits in login.conf under 2.2.5-REL
X-Send-Pr-Version: 3.2

>Number:         5466
>Category:       conf
>Synopsis:       resource limits set in login.conf don't take effect
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    steve
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan  8 14:33:39 PST 1998
>Closed-Date:    Thu Jan 22 18:30:55 PST 1998
>Last-Modified:  Thu Jan 22 18:31:48 PST 1998
>Originator:     Evan R Moore
>Release:        FreeBSD 2.2.5-RELEASE i386
>Organization:
SoverNET Inc.
>Environment:

	FBSD 2.2.5-REL with no additional patches added
	Diablo 1.13 news transit software
	256M RAM
	Pentium 166MHz

>Description:

	Here's me /etc/login.conf:

auth-defaults:\
	:auth=krb_skey_or_passwd,passwd,kerberos,skey:

auth-root-defaults:\
	:auth-login=krb_skey_or_passwd,passwd,kerberos,skey:\
	:auth-rlogin=krb_or_skey,kerberos,skey:\

auth-ftp-defaults:\
	:auth=skey_or_pwd,passwd,skey:

default|standard|root|daemon|staff|news:\
#	:cputime=infinity:\
#	:datasize-cur=16M:\
#	:stacksize-cur=8M:\
#	:memorylocked-cur=10M:\
#	:memoryuse-cur=30M:\
#	:filesize=infinity:\
#	:coredumpsize=infinity:\
#	:maxproc-cur=64:\
#	:openfiles-cur=64:\
	:cputime=infinity:\
	:filesize=infinity:\
	:datasize=infinity:\
	:stacksize=infinity:\
	:coredumpsize=infinity:\
	:memoryuse=infinity:\
	:memorylocked=infinity:\
	:maxproc=infinity:\
	:openfiles=infinity:\
	:cputime-cur=infinity:\
	:filesize-cur=infinity:\
	:datasize-cur=infinity:\
	:stacksize-cur=infinity:\
	:coredumpsize-cur=infinity:\
	:memoryuse-cur=infinity:\
	:memorylocked-cur=infinity:\
	:maxproc-cur=infinity:\
	:openfiles-cur=infinity:\
	:priority=0:\
	:requirehome@:\
	:umask=077:\
	:path=/usr/local/bin /bin /usr/bin /sbin /usr/sbin:\
	:manpath=/usr/local/man /usr/share/man:\
	:tc=auth-defaults:

	but when I login under a csh, limit gives me this:


cputime 	unlimited
filesize 	unlimited
datasize 	16384 kbytes
stacksize 	8192 kbytes
coredumpsize 	unlimited
memoryuse 	30720 kbytes
memorylocked 	10240 kbytes
maxproc 	64 
openfiles 	64 

	which is to say, the login.conf settings for datasize, stacksize,
	maxproc and openfiles didn't have any effect.  I've tried using
	real numbers, rather than infinity, and the behavior doesn't
	change.  Max limits do get set properly, but this starting
	set of soft profiles never changes.

	I'm setting up a big diablo news machine, and most of the processes
	need very high soft limits.  Ideally I'd want to disable the
	whole resource limit section of the kernel, but I like the idea
	of login.conf and want it to work.

	I've purused the source for /usr/bin/login and libutil.a, and
	don't see why things shouldn't be working.

>How-To-Repeat:

	I've not been able to undo it, so I can't tell you how to
	replicate.

>Fix:

	I haven't found it yet.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Thu Jan 22 18:30:55 PST 1998 
State-Changed-Why:  
The originator reported the problem as a typo on /etc/login.conf. 
>Unformatted:
