Date: Wed, 13 Dec 2000 12:56:19 +0600 (NOVT) From: Alexey Dokuchaev <danfe@inet.ssc.nsu.ru> To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <trond@ramstind.gtf.ol.no> Cc: FreeBSD questions <freebsd-questions@freebsd.org>, FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: How come accounting limits of login.conf still doesn't work?! Message-ID: <Pine.LNX.4.10.10012131244340.3325-100000@inet.ssc.nsu.ru> In-Reply-To: <Pine.BSF.4.21.0012121028120.28460-100000@ramstind.gtf.ol.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Dec 2000, [ISO-8859-1] Trond Endrestøl wrote: > On Tue, 12 Dec 2000, Alexey Dokuchaev wrote: > > > How come that all kewl features, such as sessionlimits, idletimes, etc all > > are documented in man login.conf(5), but never seemed to work? It's 4.2 > > already, and it still doesn't make any difference? > > One thought springs to mind, did you run > > cap_mkdb /etc/login.conf Yup, I've done this, of course. Well, technically, most of the limits (which do not involve hanging of special process to handle idletimes) work when logging in from console only. This is not quite what I need, since most of the users on my box would have ssh access only. Under linux, I used to configure PAM settings, and they applied to the user session, independent from the authentication method. Actually, PAM support in FreeBSD still seems pretty weak to me. The whole idea seems kinda, uhm... impractical, should I say? I am in no way trying to criticize the developers, I simply want those limits to be easily and uniformally configurable, and work not when logging from the console only but with ssh as well. Maybe I'm doing/getting anything wrong? Thank you. -- Yours, DAN Fe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10012131244340.3325-100000>