Actally that seems to be one of the problems.. . I just found it in the
syslog. ntpd -g should take care of this but it doesn't. The time was
intentally set to 1999 to test ntpd and see if it is working. Even with
the "-g" option I am getting:
Jan 1 01:38:38 portal ntpd[841]: time error 286216465 over 1000
seconds; set clock manually
It is as if the -g is a valid command line option but ignored.
brian moore wrote:
>
> On Wed, Jan 01, 1992 at 01:27:39AM -0600, hanasaki wrote:
> > it is serving the time fine to others but:
> > it wont set my server's time from another time server
> >
> > I have entered "server... " lines into /etc/ntp.conf
>
> If your time is too far off, ntpd will not know whether to trust the
> remote sites or yours and will refuse to change the time.
>
> --
> CueCat decoder .signature by Larry Wall:
> #!/usr/bin/perl -n
> printf "Serial: %s Type: %s Code: %s\n", map { tr/a-zA-Z0-9+-/ -_/; $_ =
> unpack
> 'u', chr(32 + length()*3/4) . $_; s/\0+$//; $_ ^= "C" x length; }
> /\.([^.]+)/g;
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
