Re: kernel 2.0.36 - 486 DX2 - clock skew?

Zygo Blaxell (uixjjji1@umail.furryterror.org)
17 Feb 1999 00:12:16 -0500


In article <19990212113226.A27277@elektroni.ee.tut.fi>,
Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi> wrote:
>On Thu, Feb 11, 1999 at 05:39:03PM +1300, Chris Wedgwood wrote:
>> This reminds me -- does xntpd/ntpd really need to lock it all of its
>> pages?
>
>I have never let it lock the pages in workstation use and it has still
>worked ok. Just comment out "#define HAVE_MLOCKALL 1" in config.h after
>configure.

I've done that too (actually I've used versions of xntpd prior to the
existence of mlockall()). If the xntpd gets swapped out during a network
transaction it will complain "previous time adjustment incomplete; residual
0.330151 sec" or some similar number. Then your time will be off by 1/3
of a second, but that corrects itself soon.

Don't do this on a peer that acts as a server for other clients, but
feel free to do it on client machines.

-- 
Zygo Blaxell, Linux Engineer, Corel Corporation, zygob@corel.ca (work),
zblaxell@furryterror.org (play).  It's my opinion, I tell you! Mine! All MINE!
Size of 'diff -Nurw [...] winehq corel' as of Tue Feb 16 23:14:00 EST 1999
Lines/files:  In 277 / 3, Out 20653 / 255, Both 20923 / 256

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/