Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.sysv386
Subject: Re: Interactive 2.2 ULIMIT problem
Message-ID: <1990Nov10.161538.11951@virtech.uucp>
Date: 10 Nov 90 16:15:38 GMT
References: <1990Nov08.024114.6923@virtech.uucp> <1990Nov8.152741.1581@pegasus.com> <1990Nov09.120821.4975@virtech.uucp> <1990Nov10.034318.602@jadpc.cts.com>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 21

In article <1990Nov10.034318.602@jadpc.cts.com> jdeitch@jadpc.cts.com (Jim Deitch) writes:
>>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.

Note that I said all processes starting jobs, not just the shell.  Only
the sh (or ksh, if you have it) read a .profile.  Even then, the user
can change it if it is in their .profile.  If it is in the /etc/profile
file then the same value applies to all users unless you put in some
additional smarts to handle it on a per-user basis.

> As I remember, a user can lower their ulimit but not raise it.

This is true, but that doesn't mean that the lower ulimit will apply
for jobs submited for execution by at or cron.
-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170