Security Basics mailing list archives
Re: User process limitations..
From: "David M. Fetter" <david.fetter () fetterconsulting com>
Date: Sat, 22 Feb 2003 16:50:13 -0800
The ulimit command would be the proper choice here. If you want in on a permanent basis then use the limit.conf file. I'm not sure why you would want/need a separate script to do the same thing? Do you have a specific reason for this?
Kenneth Hauklien wrote:
In-Reply-To: <20030221002549.GB19782 () ms210a cpsc ucalgary ca> Sorry for the weak information. Im running debian gnu linux. Ive found one sillyperl script that can check after how many processes a user / group can run but is doesnt work very well. There also found out that /etc/security/limit.conf works ( pam ). Its the same as the ulimit command. But i would very much like a script that does this.Cheers
-- David M. Fetter - http://www.fetterconsulting.com/"The world is full of power and energy and a person can go far by just skimming off a tiny bit of it." Neal Stephenson - Snow Crash
Current thread:
- User process limitations.. Kenneth Hauklien (Feb 20)
- Re: User process limitations.. Brad Arlt (Feb 20)
- Re: User process limitations.. Tarun Dua (Feb 22)
- Re: User process limitations.. camthompson (Feb 22)
- Re: User process limitations.. Nick Shapley (Feb 22)
- Re: User process limitations.. Julian Plamann (Feb 22)
- Re: User process limitations.. Johan De Meersman (Feb 22)
- RE: User process limitations.. Geert Hauwaerts (Feb 22)
- RE: User process limitations.. Bill Roe (Feb 22)
- <Possible follow-ups>
- Re: User process limitations.. Kenneth Hauklien (Feb 22)
- Re: User process limitations.. David M. Fetter (Feb 22)
- Re: User process limitations.. Brad Arlt (Feb 20)