Date: Tue, 29 Jul 1997 20:33:11 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Cc: dufault@hda.com, current@FreeBSD.ORG Subject: Re: where to put access restriction for scheduling classes Message-ID: <199707300033.UAA28927@hda.hda.com> In-Reply-To: <199707292336.TAA16191@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jul 29, 97 07:36:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> <<On Tue, 29 Jul 1997 16:31:52 -0400 (EDT), Peter Dufault <dufault@hda.com> said: > > > right thing a sysctl variable that somehow gets set during login > > via login_class while still root? Which of those are inherited > > per-process? Or do I actually add a resource and only change the > > login stuff? > > I'm sorry, I can't parse this. Let the apologies be mine. > sysctl is a SYStem ConTroL mechanism. Nothing it does is per-process. You are right. I thought that resource limits had been inhumed by sysctl, and that some were inherited. > It sounds like what you want is either a new system call to set some > flags in the proc structure, or a new sort of resource limit (if what > you're trying to restrict can easily be modeled in terms of unsigned, > nondecreasing integer values) (which effectively does the same thing > only with a bit more pre-existing infrastructure). Yes, I want something similar to number of open files per proc, as currently set by limit openfiles, without having to modify all shells in exhistence thus missing the ones I don't know about. To help with the parsing, by "only change login stuff" I meant: "Shall I add another resource limit that requires changing all shells, thus being a big pain in the neck since there must be a new gnu shell I don't know about, or, since resource limits appear to be the appropriate mechanism for what IS after all a process group resource limit in spite of this support issue, 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?" Or something like that. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707300033.UAA28927>