Date: Tue, 29 Jul 1997 16:31:52 -0400 (EDT) From: Peter Dufault <dufault@hda.com> To: current@freebsd.org Subject: where to put access restriction for scheduling classes Message-ID: <199707292031.QAA28302@hda.hda.com>
next in thread | raw e-mail | index | archive | help
I'm looking at switching from a pseudo device that sets a sysctl variable to something more mainstream to control access to sched_setscheduler. Can someone in the know explain the right thing to do - I don't want to create a new resource, so is the 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? 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?199707292031.QAA28302>