Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!ncr-sd!simasd!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: Interactive 2.2 ULIMIT problem
Message-ID: <1990Nov10.034318.602@jadpc.cts.com>
Date: 10 Nov 90 03:43:18 GMT
References: <1990Nov08.024114.6923@virtech.uucp> <1990Nov8.152741.1581@pegasus.com> <1990Nov09.120821.4975@virtech.uucp>
Organization: Network Engineering Technologies
Lines: 25

In article <1990Nov09.120821.4975@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
>In article <1990Nov8.152741.1581@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>>Or set the ULIMIT way high in the kernel and make adjustments in 
>>/etc/default/login.  That way you don't need to re-link the kernel
>>to make a change.
>
>This would be much better if the capability to set the ulimit on a per-user
>basis existed and all process starting jobs (login, cron, init) used that
>value when initiating a job for a particular user.

If you put a line in the .profile to LOWER the ulimit it will.
Correct?  As I remember, a user can lower their ulimit but not raise
it.

>-- 
>Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
>uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
>                                                Sterling, VA 22170 


-- 

UUCP: nosc!jadpc!jdeitch
ARPA: jadpc!jdeitch@nosc.mil
INET: jdeitch@jadpc.cts.com