os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Don't tell people to use some indirect method when a direct method

Browse source 
is available in order to determine which scheduler they are using.

Reviewed by:	mjg
Approved by:	bcr (mentor)
This commit is contained in:
Eitan Adler 2012-10-30 12:01:18 +00:00
parent f3495d4402
commit 88ba468ed9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=39853
1 changed files with 1 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

17
en_US.ISO8859-1/books/faq/book.xml
View file

@ -4488,27 +4488,12 @@ device sio5 at isa? port 0x2b8 tty flags 0x501 vector siointr</programlisting>
</question>
<answer>
<para>Check for the existence of the
<varname>kern.sched.quantum</varname> sysctl. If you have
it, you should see something like this:</para>
<screen>&prompt.user; sysctl <replaceable>kern.sched.quantum</replaceable>
kern.sched.quantum: 99960</screen>
<para>If the <varname>kern.sched.quantum</varname> sysctl
exists, you are using the 4BSD scheduler (&man.sched.4bsd.4;).
If not, you will get an error printed by &man.sysctl.8;
(which you can safely ignore):</para>
<screen>&prompt.user; sysctl <replaceable>kern.sched.quantum</replaceable>
sysctl: unknown oid 'kern.sched.quantum'</screen>
<para>The name of the scheduler currently being used is
directly available as the value of the
<varname>kern.sched.name</varname> sysctl:</para>
<screen>&prompt.user; sysctl <replaceable>kern.sched.name</replaceable>
kern.sched.name: 4BSD</screen>
kern.sched.name: ULE</screen>
</answer>
</qandaentry>