Problem
When running xntpd, any additional process that is 100% CPU-intensive causes xntpd to stall.
Cause
xntpd, the Network Time Protocol daemon, was designed to do a system call to give its process the highest possible priority in order to minimize time jitter in its calculations. Unfortunately, it was programmed to request the lowest possible priority. This is normally only a minor problem, as time will jitter slightly more than it should.
However, when you run a program that causes the CPU to be 100% busy, like SETI@Home or a distributed encryption cracking program such as RC5DES, xntpd has actually requested such a low priority that it will never get to run on such a system.
Solution
Currently, there are no workarounds available from SCO. The fix
for this problem has been incorporated into the newest public
domain source for the NTP protocol suite. SCO does not yet
provide a binary distribution containing the fix, but you can
download the source and build your own version.This is scheduled to be addressed in a future release of SCO OpenServer 5.
See also
Manual page: xntpd(ADMN)ta107619, "How do I configure xntpd(ADMN) to alter timekeeping limitations?"