Date: Tue, 29 Jul 1997 19:36:33 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Peter Dufault <dufault@hda.com> Cc: current@FreeBSD.ORG Subject: where to put access restriction for scheduling classes Message-ID: <199707292336.TAA16191@khavrinen.lcs.mit.edu> In-Reply-To: <199707292031.QAA28302@hda.hda.com> References: <199707292031.QAA28302@hda.hda.com>
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. sysctl is a SYStem ConTroL mechanism. Nothing it does is per-process. 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). -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?199707292336.TAA16191>