From owner-freebsd-hackers Wed Apr 12 1:48: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id B14AA37B941 for ; Wed, 12 Apr 2000 01:48:04 -0700 (PDT) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-314.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FSW001BPB3ZMB@mail.uni-bielefeld.de> for freebsd-hackers@freebsd.org; Wed, 12 Apr 2000 10:48:01 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id IAA00264; Wed, 12 Apr 2000 08:01:37 +0200 (CEST envelope-from bjoern) Date: Wed, 12 Apr 2000 08:01:36 +0200 From: Bjoern Fischer Subject: Re: efficiency of maxproc hardlimit In-reply-to: <20000411100950.E4381@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Apr 11, 2000 at 10:09:50AM -0700 To: Alfred Perlstein Cc: freebsd-hackers@freebsd.org Message-id: <20000412080136.A239@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <20000410094436.A778@frolic.no-support.loc> <20000410013139.R4381@fw.wintelcom.net> <20000411125643.A282@frolic.no-support.loc> <20000411100950.E4381@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 11, 2000 at 10:09:50AM -0700, Alfred Perlstein wrote: [...] > It's also silly. If you've found limits that "work" then why insist > on giving your users enough rope to hang you? The world is complicated. Some of my processes need that stacksize. There is no problem setting safe limits for all other users or denying access to my machine completely but for myself (this is the case now). > Either enforce proper limits or rmuser. Of course. But the users behave quite well, so no real complaints. > If you could get a traceback of the stuck client, that would be > helpful. Ok, I'm working on that but it may take some time. Some long run processes started yesterday may need a few days and I don't want to disturb them. btw. don't the BSDI guys have a mechanism for stopping a running process storing the image somewhere in swap space and continue after a reboot? Would be quite handy right now. Thank you for your suggestions. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message