Date: Tue, 27 Apr 1999 22:07:42 -0400 From: Nathan Dorfman <nathan@rtfm.net> To: Andrzej Bialecki <abial@webgiro.com> Cc: Stephane Legrand <Stephane.Legrand@wanadoo.fr>, Luigi Rizzo <luigi@labinfo.iet.unipi.it>, current@FreeBSD.ORG Subject: Re: does login.conf limitations work ? Message-ID: <19990427220742.A4971@rtfm.net> In-Reply-To: <Pine.BSF.4.05.9904241637400.25684-100000@freja.webgiro.com>; from Andrzej Bialecki on Sat, Apr 24, 1999 at 04:39:20PM %2B0200 References: <199904241337.PAA01205@sequoia.mondomaineamoi.megalo> <Pine.BSF.4.05.9904241637400.25684-100000@freja.webgiro.com>
index | next in thread | previous in thread | raw e-mail
On Sat, Apr 24, 1999 at 04:39:20PM +0200, Andrzej Bialecki wrote: > On Sat, 24 Apr 1999, Stephane Legrand wrote: > > > > That's also my impression. I glipmsed the whole source tree and I couldn't > > > find any place where the limits are enforced. BTW. what entity should > > > enforce login time limits? Kernel? Some user-space daemon? > > > > > > > To report a login.conf success, i've used on a 2.2.8 system the > > "cputime" ressource limit. I set it to zero and that worked very > > well. So may be only some limits are implemented ? cputime is just a plain old process rlimit. Implementing it should be as easy as calling setrlimit(). On the other hand, login time is a different story. Generally I've found that most of the stuff in login.conf, at least that which does things like setting rlimits, environment, and modifying some login behavior (motd, nologin, mail check, etc.) works. -- Nathan Dorfman <nathan@rtfm.net> The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the messagehelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990427220742.A4971>