Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Jul 1997 21:26:58 -0400 (EDT)
From:      Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To:        Peter Dufault <dufault@hda.com>
Cc:        current@FreeBSD.ORG
Subject:   Re: where to put access restriction for scheduling classes
Message-ID:  <199707300126.VAA16803@khavrinen.lcs.mit.edu>
In-Reply-To: <199707300033.UAA28927@hda.hda.com>
References:  <199707292336.TAA16191@khavrinen.lcs.mit.edu> <199707300033.UAA28927@hda.hda.com>

next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 29 Jul 1997 20:33:11 -0400 (EDT), Peter Dufault
<dufault@hda.com> said:

> "Shall I add another resource limit that requires changing all
> shells, [...] or [...] shall I add a resource limit to FreeBSD and
> change only that part of the FreeBSD login mechanism that is
> modifying resource limits at login time while still effectively root
> thus ignore this portability af shells issue, in particular ignoring
> the other 4.4 derived OS's?"

No shell should break as a result of defining a new resource limit.
Therefore, you should update setusercontext(3) and the two system
shells, and let the other shells fend for themselves.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707300126.VAA16803>