Date: Thu, 31 Jul 1997 00:43:47 +1000 From: David Nugent <davidn@labs.usn.blaze.net.au> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Peter Dufault <dufault@hda.com>, current@FreeBSD.ORG Subject: Re: where to put access restriction for scheduling classes Message-ID: <199707301443.AAA00985@labs.usn.blaze.net.au> In-Reply-To: Your message of "Tue, 29 Jul 1997 21:26:58 -0400." <199707300126.VAA16803@khavrinen.lcs.mit.edu>
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. Don't forget /usr/bin/limits. :-) Just out of curiosity, what type of resource are we actually discussing here? -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707301443.AAA00985>