From owner-freebsd-hackers Mon Jun 16 13:20:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA28012 for hackers-outgoing; Mon, 16 Jun 1997 13:20:35 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA28007; Mon, 16 Jun 1997 13:20:32 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA18033; Mon, 16 Jun 1997 13:10:57 -0700 From: Terry Lambert Message-Id: <199706162010.NAA18033@phaeton.artisoft.com> Subject: Re: help, running out of processes. :( To: tom@sdf.com (Tom Samplonius) Date: Mon, 16 Jun 1997 13:10:56 -0700 (MST) Cc: terry@lambert.org, joe@pavilion.net, questions@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Jun 15, 97 11:18:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > login.conf only operates agains users whose credentials were generated > > through a login process (quotas are assigned at the time credentials > > are, when using login.conf). > > Yes, a big problem for processes that leave root after binding to a > privileged port. > > But shouldn't such processes should call setrlimit() appropriately > first? Good question; but it begs the question "what is a credential?". I suspect it's unreasonable to have processes started in the rc.conf file calling setrlimit() as a required action. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.