Re: Ntpd assistance

2004-09-23 Thread MikeM
On 9/22/2004 at 11:58 AM alden.pierre wrote:

|MikeM wrote:
|
|>On 9/22/2004 at 11:19 AM alden.pierre wrote:
|>
|>|/etc/rc.conf contains the following:
|>|
|>|ntpdate_enable="YES"
|>|ntpdate_flags="timex.cs.columbia.edu"
|>|xntpd_enable="YES"# Run ntpd Network Time Protocol
|>|
|>|/etc/ntpd.conf contains the following:
|>|
|>|driftfile/etc/ntp/drift
|>|server 65.211.109.1
|>|server 65.211.109.11
|>|server 209.51.161.238
|>|server 128.59.59.177
|>|
|>|
|>|Am I doing something wrong here?  My time seems to go out of sync after 
|>|my FreeBSD 4.10 box has been up for a couple of hours.  Any help would 
|>|be greatly appreciated.
|> =


A couple of other suggestions:

1) Add the -sv flag to the ntpdate flags:

ntpdate_flags="-sv timex.cs.columbia.edu"

That will give you some good ntpdate info in the messages log file.


2) Add the following to yout ntp.conf file:

# enable logging
logfile /var/log/ntp.log

That will give you some info on the ntpd daemon.





___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-23 Thread MikeM
On 9/22/2004 at 11:58 AM alden.pierre wrote:

|MikeM wrote:
|
|>On 9/22/2004 at 11:19 AM alden.pierre wrote:
|>
|>|/etc/rc.conf contains the following:
|>|
|>|ntpdate_enable="YES"
|>|ntpdate_flags="timex.cs.columbia.edu"
|>|xntpd_enable="YES"# Run ntpd Network Time Protocol
|>|
|>|/etc/ntpd.conf contains the following:
|>|
|>|driftfile/etc/ntp/drift
|>|server 65.211.109.1
|>|server 65.211.109.11
|>|server 209.51.161.238
|>|server 128.59.59.177
|>|
|>|
|>|Am I doing something wrong here?  My time seems to go out of sync after 
|>|my FreeBSD 4.10 box has been up for a couple of hours.  Any help would 
|>|be greatly appreciated.
|> =
|>
|>Post the results of the command
|>
|> ntpq -c peer
|>  
|>
|No association ID's returned
|
|Is what I get.
|
|Thank You
|Alden Louis-Pierre
 =

It looks like the ntpd daemon isn't running.  I note the ntpd.conf typo you
had.  Does changing it to ntp.conf resolve your problem?

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


RE: Ntpd assistance

2004-09-23 Thread James Hong
 i had a machine where internal clock runs 1.5 times faster than normal
clock.
as a result time will be about 5min faster every 30min or so.
if internal clock is busted like mine, ntpd will not be able to sync time.
It takes as long as few days to sync few min on your unix clock.

Also if i remember correctly unix keeps internal clock and system clock
separatly.

read 
http://www.eecis.udel.edu/~mills/ntp/html/ntpd.html


PS. use closer tier 2 or tier 3  and multiple sources (as long as they are
public)


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Sent: Thursday, September 23, 2004 2:37 PM
To: [EMAIL PROTECTED]
Subject: Re: Ntpd assistance

alden.pierre wrote:
> /etc/rc.conf contains the following:
> 
> ntpdate_enable="YES"
> ntpdate_flags="timex.cs.columbia.edu"
> xntpd_enable="YES"# Run ntpd Network Time Protocol
> 
> /etc/ntpd.conf contains the following:
> 
> driftfile/etc/ntp/drift
> server 65.211.109.1
> server 65.211.109.11
> server 209.51.161.238
> server 128.59.59.177

Use /etc/ntp.conf (NOT ntpd.conf).

I would configure this system as follows:

/etc/rc.conf:

ntpdate_enable="YES"
ntpdate_flags="-b 65.211.109.1 65.211.109.11 209.51.161.238 128.59.59.177"
xntpd_enable="YES"


/etc/ntp.conf:

#--
# prohibit general access to this service
#--
restrict default ignore

#--
# localhost has full access to the server
#--
restrict 127.0.0.1

#--
# servers to query
#--
server 65.211.109.1
restrict 65.211.109.1

server 65.211.109.11
restrict 65.211.109.11

server 209.51.161.238
restrict 209.51.161.238

server 128.59.59.177
restrict 128.59.59.177

#--
# files to use
#--
driftfile /var/db/ntp.drift


-

The idea is, that, at boot up, you force instant time synchronization with
ntpdate, using the list of servers in ntpdate_flags="-b ".
(check the man page of ntpdate and the -b flag).
Then you allow ntpd to start (xntpd_enable = "YES"), that will keep the time
in sync with the servers in /etc/ntp.conf.
As a regular user, verify nptd's sync behaviour with:

ntpq -np

I hope that helps.
Rob.


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Rob
alden.pierre wrote:
/etc/rc.conf contains the following:
ntpdate_enable="YES"
ntpdate_flags="timex.cs.columbia.edu"
xntpd_enable="YES"# Run ntpd Network Time Protocol
/etc/ntpd.conf contains the following:
driftfile/etc/ntp/drift
server 65.211.109.1
server 65.211.109.11
server 209.51.161.238
server 128.59.59.177
Use /etc/ntp.conf (NOT ntpd.conf).
I would configure this system as follows:
/etc/rc.conf:
ntpdate_enable="YES"
ntpdate_flags="-b 65.211.109.1 65.211.109.11 209.51.161.238 128.59.59.177"
xntpd_enable="YES"
/etc/ntp.conf:
#--
# prohibit general access to this service
#--
restrict default ignore
#--
# localhost has full access to the server
#--
restrict 127.0.0.1
#--
# servers to query
#--
server 65.211.109.1
restrict 65.211.109.1
server 65.211.109.11
restrict 65.211.109.11
server 209.51.161.238
restrict 209.51.161.238
server 128.59.59.177
restrict 128.59.59.177
#--
# files to use
#--
driftfile /var/db/ntp.drift
-
The idea is, that, at boot up, you force instant time synchronization
with ntpdate, using the list of servers in ntpdate_flags="-b ".
(check the man page of ntpdate and the -b flag).
Then you allow ntpd to start (xntpd_enable = "YES"), that will keep
the time in sync with the servers in /etc/ntp.conf.
As a regular user, verify nptd's sync behaviour with:
   ntpq -np
I hope that helps.
Rob.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Bill Moran
Emanuel Strobl <[EMAIL PROTECTED]> wrote:

> Am Mittwoch, 22. September 2004 23:43 schrieb Bill Moran:
> [...]
> > > > I don't believe you can reliably run both ntpdate and xntpd.  Besides,
> > >
> > > This is working because ntpdate is invoked only once at startup, which
> > > is, in my case, because of possible empty BIOS-Battery where the date
> > > would be wrong for several years which causes ntpd to refuse to adjust
> > > the time. I use generally ntpdate at startup before ntpd keeps the kernel
> > > time in sync.
> >
> > Um ... did you read my whole message?
> 
> Sorry, no. You're right, next time I'll be more careful.

Sorry ... I didn't mean to be short about it.  I should take a deep
breath before sending off mails like that.

Just having a tough day, I apologize for taking it out on you.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Emanuel Strobl
Am Mittwoch, 22. September 2004 23:43 schrieb Bill Moran:
[...]
> > > I don't believe you can reliably run both ntpdate and xntpd.  Besides,
> >
> > This is working because ntpdate is invoked only once at startup, which
> > is, in my case, because of possible empty BIOS-Battery where the date
> > would be wrong for several years which causes ntpd to refuse to adjust
> > the time. I use generally ntpdate at startup before ntpd keeps the kernel
> > time in sync.
>
> Um ... did you read my whole message?

Sorry, no. You're right, next time I'll be more careful.

Thanks,

-Mano

>
> Check the ntpd man page on the -g option.  If you are running ntpd, you
> don't need ntpdate.  You answer shows that you are not familiar with the
> ntpd program and didn't read the rest of my email.
>
> > > if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will
> > > behave the same as ntpdate at startup, as well as running continually
> > > to ensure your clock stays synced.


pgpBHcx6tzWa8.pgp
Description: PGP signature


Re: Ntpd assistance

2004-09-22 Thread Bill Moran
Emanuel Strobl <[EMAIL PROTECTED]> wrote:

> Am Mittwoch, 22. September 2004 23:27 schrieb Bill Moran:
> > Emanuel Strobl <[EMAIL PROTECTED]> wrote:
> > > Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre:
> > > > /etc/rc.conf contains the following:
> > > >
> > > > ntpdate_enable="YES"
> > > > ntpdate_flags="timex.cs.columbia.edu"
> > > > xntpd_enable="YES"# Run ntpd Network Time Protocol
> > > >
> > > > /etc/ntpd.conf contains the following:
> > >
> > >^
> > >
> > > Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of
> > > ntpd.conf?
> > >
> > > You can try -c /etc/ntpd.conf
> > >
> > > -Harry
> >
> > In addition to this minor error ...
> >
> > I don't believe you can reliably run both ntpdate and xntpd.  Besides,
> 
> This is working because ntpdate is invoked only once at startup, which is, in 
> my case, because of possible empty BIOS-Battery where the date would be wrong 
> for several years which causes ntpd to refuse to adjust the time.
> I use generally ntpdate at startup before ntpd keeps the kernel time in sync.

Um ... did you read my whole message?

Check the ntpd man page on the -g option.  If you are running ntpd, you
don't need ntpdate.  You answer shows that you are not familiar with the
ntpd program and didn't read the rest of my email.
 
> > if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will
> > behave the same as ntpdate at startup, as well as running continually
> > to ensure your clock stays synced.
> 


-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Emanuel Strobl
Am Mittwoch, 22. September 2004 23:27 schrieb Bill Moran:
> Emanuel Strobl <[EMAIL PROTECTED]> wrote:
> > Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre:
> > > /etc/rc.conf contains the following:
> > >
> > > ntpdate_enable="YES"
> > > ntpdate_flags="timex.cs.columbia.edu"
> > > xntpd_enable="YES"# Run ntpd Network Time Protocol
> > >
> > > /etc/ntpd.conf contains the following:
> >
> >^
> >
> > Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of
> > ntpd.conf?
> >
> > You can try -c /etc/ntpd.conf
> >
> > -Harry
>
> In addition to this minor error ...
>
> I don't believe you can reliably run both ntpdate and xntpd.  Besides,

This is working because ntpdate is invoked only once at startup, which is, in 
my case, because of possible empty BIOS-Battery where the date would be wrong 
for several years which causes ntpd to refuse to adjust the time.
I use generally ntpdate at startup before ntpd keeps the kernel time in sync.

-Mano

> if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will
> behave the same as ntpdate at startup, as well as running continually
> to ensure your clock stays synced.


pgpnyYQI0oEjD.pgp
Description: PGP signature


Re: Ntpd assistance

2004-09-22 Thread Bill Moran
Emanuel Strobl <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre:
> > /etc/rc.conf contains the following:
> >
> > ntpdate_enable="YES"
> > ntpdate_flags="timex.cs.columbia.edu"
> > xntpd_enable="YES"# Run ntpd Network Time Protocol
> >
> > /etc/ntpd.conf contains the following:
>^
> 
> Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of 
> ntpd.conf?
> 
> You can try -c /etc/ntpd.conf
> 
> -Harry

In addition to this minor error ...

I don't believe you can reliably run both ntpdate and xntpd.  Besides,
if you plan to run xntpd anyway, just set xntpd_flags="-g" and it will
behave the same as ntpdate at startup, as well as running continually
to ensure your clock stays synced.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Mike Hogsett
Richard Lynch wrote:
Am I doing something wrong here?  My time seems to go out of sync after
my FreeBSD 4.10 box has been up for a couple of hours.  Any help would
be greatly appreciated.
After your machine has booted and run in multiuser mode for several minutes
run ntpdc to query ntpd about its status.  The command to see its status with
its time servers is 'peers', e.g.
;ntpdc
ntpdc> peers
 remote   local  st poll reach  delay   offsetdisp
===
*zeus.csl.sri.co 130.107.2.57 2 1024  377 0.00079  0.000651 0.01483
=plato.csl.sri.c 130.107.2.57 3 1024  377 0.00035 -0.001401 0.01483
=orion.csl.sri.c 130.107.2.57 3 1024  377 0.00032 -0.001799 0.01483
ntpdc>
It was posted here recenlty that if your security setting is at 1 (?),
then ntp can only change the clock by 1 second...
init(8) states secure level 2 or above.
 - Mike
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Richard Lynch
alden.pierre wrote:
> /etc/rc.conf contains the following:
>
> ntpdate_enable="YES"
> ntpdate_flags="timex.cs.columbia.edu"
> xntpd_enable="YES"# Run ntpd Network Time Protocol
>
> /etc/ntpd.conf contains the following:
>
> driftfile/etc/ntp/drift
> server 65.211.109.1
> server 65.211.109.11
> server 209.51.161.238
> server 128.59.59.177
>
>
> Am I doing something wrong here?  My time seems to go out of sync after
> my FreeBSD 4.10 box has been up for a couple of hours.  Any help would
> be greatly
> appreciated.

It was posted here recenlty that if your security setting is at 1 (?),
then ntp can only change the clock by 1 second...

-- 
Like Music?
http://l-i-e.com/artists.htm

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread Emanuel Strobl
Am Mittwoch, 22. September 2004 17:19 schrieb alden.pierre:
> /etc/rc.conf contains the following:
>
> ntpdate_enable="YES"
> ntpdate_flags="timex.cs.columbia.edu"
> xntpd_enable="YES"# Run ntpd Network Time Protocol
>
> /etc/ntpd.conf contains the following:
   ^

Correct me if I'm wrong but doesn't ntpd 4.1 use ntp.conf instead of 
ntpd.conf?

You can try -c /etc/ntpd.conf

-Harry

>
> driftfile/etc/ntp/drift
> server 65.211.109.1
> server 65.211.109.11
> server 209.51.161.238
> server 128.59.59.177
>
>
> Am I doing something wrong here?  My time seems to go out of sync after
> my FreeBSD 4.10 box has been up for a couple of hours.  Any help would
> be greatly
> appreciated.
>
> Thank You
> Alden Louis-Pierre
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"


pgpmdhWNQg7CO.pgp
Description: PGP signature


Re: Ntpd assistance

2004-09-22 Thread Mikko Heiskanen
alden.pierre wrote:
/etc/rc.conf contains the following:
ntpdate_enable="YES"
ntpdate_flags="timex.cs.columbia.edu"
xntpd_enable="YES"# Run ntpd Network Time Protocol
/etc/ntpd.conf contains the following:
driftfile/etc/ntp/drift
server 65.211.109.1
server 65.211.109.11
server 209.51.161.238
server 128.59.59.177
Am I doing something wrong here?  My time seems to go out of sync after 
my FreeBSD 4.10 box has been up for a couple of hours.  Any help would 
be greatly
appreciated.

Thank You
Alden Louis-Pierre
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
"[EMAIL PROTECTED]"
man ntpd and ntpdate show that these are two different things.
Ntpdate makes clock sync in restart, xntpd keeps it that way.
ntpdate, to my understanding, doesn't use the config file.
Mikko
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread alden.pierre
MikeM wrote:
On 9/22/2004 at 11:19 AM alden.pierre wrote:
|/etc/rc.conf contains the following:
|
|ntpdate_enable="YES"
|ntpdate_flags="timex.cs.columbia.edu"
|xntpd_enable="YES"# Run ntpd Network Time Protocol
|
|/etc/ntpd.conf contains the following:
|
|driftfile/etc/ntp/drift
|server 65.211.109.1
|server 65.211.109.11
|server 209.51.161.238
|server 128.59.59.177
|
|
|Am I doing something wrong here?  My time seems to go out of sync after 
|my FreeBSD 4.10 box has been up for a couple of hours.  Any help would 
|be greatly appreciated.
=

Post the results of the command
ntpq -c peer
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
 

No association ID's returned
Is what I get.
Thank You
Alden Louis-Pierre
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Ntpd assistance

2004-09-22 Thread MikeM
On 9/22/2004 at 11:19 AM alden.pierre wrote:

|/etc/rc.conf contains the following:
|
|ntpdate_enable="YES"
|ntpdate_flags="timex.cs.columbia.edu"
|xntpd_enable="YES"# Run ntpd Network Time Protocol
|
|/etc/ntpd.conf contains the following:
|
|driftfile/etc/ntp/drift
|server 65.211.109.1
|server 65.211.109.11
|server 209.51.161.238
|server 128.59.59.177
|
|
|Am I doing something wrong here?  My time seems to go out of sync after 
|my FreeBSD 4.10 box has been up for a couple of hours.  Any help would 
|be greatly appreciated.
 =

Post the results of the command

 ntpq -c peer


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"