On 2000-Feb-03 20:11:57 +1100, Bruce Evans <[EMAIL PROTECTED]> wrote:
> ntp is
>doing well if it falls back to another method after the syscalls fail.
ntpd iterates (at runtime) through all the possible scheduling
mechanisms that were enabled at compile time, until one works. These
are (in order) SetPriorityClass() (LoseNT only), sched_setscheduler(),
rtprio(), nice(), setpriority(). If all these fail, it will log a
message that it couldn't improve it's priority - in which case it will
still function, but probably won't be as accurate. (ntpd is probably
a special case, in that the P1003.1b functions aren't essential to it,
they just improve its operation).
>(The syscalls are kind enough to return ENOSYS without generating a
>SIGSYS like normal unsupported syscalls.)
/sys/posix4/p1003_1b.c uses syscall_not_present() as a stub routine,
this includes the comment 'a " return nosys(p, uap); " here causes a
core dump.' and returns ENOSYS. I'm not sure who wrote this comment.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
