From owner-freebsd-questions Fri Jun 22 22:41:17 2001 Delivered-To: freebsd-questions@freebsd.org Received: from shumai.marcuscom.com (rdu26-228-058.nc.rr.com [66.26.228.58]) by hub.freebsd.org (Postfix) with ESMTP id 4595837B401 for ; Fri, 22 Jun 2001 22:41:11 -0700 (PDT) (envelope-from marcus@marcuscom.com) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.3/8.11.3) with ESMTP id f5N5fEh04380; Sat, 23 Jun 2001 01:41:14 -0400 (EDT) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Sat, 23 Jun 2001 01:41:14 -0400 (EDT) From: Joe Clarke To: "Rex A. Roof" Cc: Subject: Re: login.conf restrictions In-Reply-To: <20010623001321.A19970@rexroof.com> Message-ID: <20010623014059.J92463-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You need to run cap_mkdb. Only the login.conf.db is actually read. Joe Clarke On Sat, 23 Jun 2001, Rex A. Roof wrote: > On Fri, Jun 22, 2001 at 11:53:50PM -0400, Joe Clarke wrote: > > Right before you start these daemons, get the output of limit (or limits), > > and see what the logged in user is imposed with. Those will be the > > resource restrictions imposed on your process. You should grant root as > > close to unlimited resources as possible for the purposes of starting > > these daemons. > > related question: > > when changes are made to the login.conf, is running cap_mkdb on > it optional? what effect does it have? the man page isn't super clear. > the changes take place right away on any subsequent logins? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message