From owner-freebsd-current Tue Feb 4 12:43:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA10760 for current-outgoing; Tue, 4 Feb 1997 12:43:57 -0800 (PST) Received: from vex.net (shell.vex.net [207.107.242.162]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA10751 for ; Tue, 4 Feb 1997 12:43:52 -0800 (PST) Received: from vex.net(really [207.107.242.162]) by vex.net via sendmail with smtp id for ; Tue, 4 Feb 1997 15:43:44 -0500 (EST) (Smail-3.2.0.90 1996-Dec-4 #4 built 1997-Jan-8) Date: Tue, 4 Feb 1997 15:43:43 -0500 (EST) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: /etc/login.conf and xdm logins In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 4 Feb 1997, Brian Tao wrote: > > I can't seem to raise my resource limits above 256 open files and 32 > processes, regardless of my login class in /etc/master.passwd and > the settings in /etc/login.conf. Never mind... I figured some of it out. I'm launching xdm from /etc/rc.local, which means it assumes the login class of "daemon". I raised the daemon class limits, rebooted, and the changes held. My next question is: since xdm runs as root, it should be able to raise hard resource limits for child processes, right? Do I still need to tweak xdm so that my login class is recognized upon login? Right now, it appears that everyone inherits daemon's resource limits. -- Brian Tao (BT300, taob@risc.org) "Though this be madness, yet there is method in't"