Does timed have some major 64 bit issues or something?  Trying to run timed on
my 5.0 alpha from a 4.4 x86 box proves disastrous.  5.0 x86 clients work fine. 
The alpha keeps getting its date set back into 1970:

Nov 19 14:06:02 baz timed[379]: slave to in.cx
Jan  2 21:35:41 baz timed[379]: date changed by in.cx from Mon Nov 19 14:06:02
2001
19 Nov 14:07:49 ntpdate[533]: step time server 216.34.144.7 offset
1006002718.410080 sec

(I ran ntpdate manually after killing timed.)

On x86 the messages look like so:

Nov 19 13:14:05 deimos timed[425]: slave to server.baldwin.cx
Nov 19 13:13:42 deimos timed[425]: date changed by server.baldwin.cx from Mon
Nov 19 13:14:05 2001 

And work fine.  Also, FWIW, timed spits out a bunch of unaligned access
warnings when it starts up on alpha.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to