Date: Mon, 9 Feb 2004 11:25:22 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: sammy!!! <sammy@lost-angel.com> Cc: current@freebsd.org Subject: Re: Can't login to 5.2-RC1, must hard reboot Message-ID: <20040209112359.S48001@carver.gumbysoft.com> In-Reply-To: <E9EE4535-59C7-11D8-B177-0003934BF296@lost-angel.com> References: <E9EE4535-59C7-11D8-B177-0003934BF296@lost-angel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 7 Feb 2004, sammy!!! wrote: > I get the following error messages in my logfile, a lot. > > Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit > datasize: Operation not permitted > Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit > stacksize: Operation not permitted > Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit > maxproc: Operation not permitted > Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit > openfiles: Operation not permitted Looks like you've configured a custom login class (in /etc/login.conf), and set the limits higher than you're allowed to as a user. Check that the limits set in /etc/login.conf are appropriate, then use cap_mkdb to rebuild the database. Considering you have an aac controller, you are probably hitting the getblk off-by-one bug that Scott fixed the other day. Update your -current or apply the patch from the lists. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209112359.S48001>