Date: Thu, 2 Feb 1995 17:02:29 -0700 From: osyjm@schizo.coe.montana.edu (Jaye Mathisen) To: Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> Cc: osyjm@schizo.coe.montana.edu (Jaye Mathisen), roberto@blaise.ibp.fr (Ollivier ROBERT), guido@gvr.win.tue.nl (Guido van Rooij), FreeBSD-hackers@freefall.cdrom.com Subject: Re: limits (again) Message-ID: <9502030002.AA17625@schizo.coe.montana.edu> In-Reply-To: <9502022344.AA22142@halloran-eldar.lcs.mit.edu> References: <199502022127.WAA17861@gvr.win.tue.nl> <9502022240.AA17211@blaise.ibp.fr> <9502022253.AA17337@schizo.coe.montana.edu> <9502022344.AA22142@halloran-eldar.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Garrett" == Garrett Wollman <wollman@halloran-eldar.lcs.mit.edu> writes:
Garrett> <<On Thu, 2 Feb 1995 15:53:00 -0700,
Garrett> osyjm@schizo.coe.montana.edu (Jaye Mathisen) said:
>> Heck, if it's wish-time, I'd love to see limits on # of
>> processes/user, limits on pty vs tty access,
>> time-of-day-limits, sheesh, a whole bunch of 'em.
Garrett> Only the first of these is any business of the kernel's.
Garrett> As for the rest, that's what the `pw_class' hook in the
Garrett> password database is for.
Well, the stuff in the pwdb seems useful at logon, it looks harder to
make use of it constantly. ie, it's fine if they login before 5pm, but
when 5pm rolls around, I want their jobs killed, and them booted. That
looks easier in the kernel as opposed to login and some daemon.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9502030002.AA17625>