Path: utzoo!attcan!uunet!virtech!cpcahil From: cpcahil@virtech.uucp (Conor P. Cahill) Newsgroups: comp.unix.sysv386 Subject: Re: Interactive 2.2 ULIMIT problem Message-ID: <1990Nov09.120821.4975@virtech.uucp> Date: 9 Nov 90 12:08:21 GMT References: <113@genco.bungi.com> <1990Nov08.024114.6923@virtech.uucp> <1990Nov8.152741.1581@pegasus.com> Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill) Organization: Virtual Technologies Inc., Sterling VA Lines: 18 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. The other problem with setting it in login to be different from the kernel setting is that depending upon how the job got executed, the ulimit will be different (if it got executed from cron it would have the kernel ulimit unless cron was restarted since the boot). -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170