From owner-freebsd-hackers Thu Aug 7 18:09:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA12417 for hackers-outgoing; Thu, 7 Aug 1997 18:09:22 -0700 (PDT) Received: from labs.usn.blaze.net.au (root@labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA12409 for ; Thu, 7 Aug 1997 18:09:16 -0700 (PDT) Received: from labs.usn.blaze.net.au (davidn@local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id LAA03873; Fri, 8 Aug 1997 11:07:43 +1000 (EST) Message-Id: <199708080107.LAA03873@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Alan Batie Cc: hackers@freebsd.org Subject: Re: login classes In-reply-to: Your message of "Mon, 04 Aug 1997 14:18:52 MST." <19970804141852.47074@aahz.jf.intel.com> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Aug 1997 11:07:41 +1000 From: David Nugent Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > per-user process limit). I've already hacked cron to add them in, and > now it looks like I need to hack smrsh so that vacation will run. Hmm. Since sendmail runs at daemon resource level, this is the problem here, regardless of which user it is deliverying to. Changing your effective uid does not affect resources. You're arguing it should, and that argument has merrit. However, as in this case, it may not really be appropriate in all cases. Certainly the kernel can't really know much about per-user resource settings. It would make it simpler from an api point of view, but it would probably result it being less configurable and flexible (pretty much like we had before). > God help me if sendmail gives up root before invoking smrsh and I have to > hack *it*. Especially when I have two days left before I leave... I don't see why this is necessary. Increase resources in your *daemon* class since that's what applies here. The user's resources aren't involved except when it comes to counting resource use for that user. > Here's the patch to cron: Cron in 2.2-stable has already been fixed to use user class resources as of a couple of weeks ago. Its original omission was an oversight. Regards, David -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/