Re: NTP packages (was: setting hardware clock from NIST)

2003-11-06 Thread Paul E Condon
On Wed, Nov 05, 2003 at 10:13:45PM -0800, [EMAIL PROTECTED] wrote: Can someone summarize the different ntp packages? For example what to run on a server vs. on an internal NAT'ed workstation. I use chrony on all my machines. One machine is my access to the net. It points to the

Re: NTP packages (was: setting hardware clock from NIST)

2003-11-06 Thread Bob Proulx
[EMAIL PROTECTED] wrote: Can someone summarize the different ntp packages? In the beginning systems were isolated. There was no net. Then UUCP brought light unto the darkness. This was called USENET and we saw that it was good. [It is a unix list so I am not mentioning fidonet.] These

UUCP Usenet (was Re: NTP packages (was: setting hardware clock from NIST))

2003-11-06 Thread Ron Johnson
On Thu, 2003-11-06 at 01:07, Bob Proulx wrote: [EMAIL PROTECTED] wrote: Can someone summarize the different ntp packages? In the beginning systems were isolated. There was no net. Then UUCP brought light unto the darkness. This was called USENET and we saw I thought that

Re: NTP packages (was: setting hardware clock from NIST)

2003-11-06 Thread John Hasler
Bob Proulx writes: Let me hazard a guess that chrony is not a full implementation Chrony provides complete time service. Ntpd does do things that Chrony doesn't but they are things like supporting atomic clock hardware and providing obscure encryption schemes. As mentioned elsewhere in this

Re: NTP packages (was: setting hardware clock from NIST)

2003-11-06 Thread John Hasler
Paul Condon writes: Chrony ins a wrapper around ntp... No. Chrony is an independent implementation of the NTP protocol. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?

Re: setting hardware clock from NIST

2003-11-06 Thread David Z Maze
[EMAIL PROTECTED] (Haines Brown) writes: From: David Z Maze [EMAIL PROTECTED] It's almost certainly better to find a local time server and not hammer on the NIST's; I'd also use ntp (ntp-simple package) to keep your clock up-to-date while the system is running. ... Thanks for the advice.

Re: setting hardware clock from NIST

2003-11-06 Thread Haines Brown
From: David Z Maze [EMAIL PROTECTED] If you install ntp-simple it will start a daemon that will periodically poll the time servers and gently keep your clock in sync. (If you're five seconds off, that time will be made up gradually, rather than abruptly shifting the clock.) No need to set

Re: UUCP Usenet (was Re: NTP packages (was: setting hardware clock from NIST))

2003-11-06 Thread Bob Proulx
Ron Johnson wrote: Bob Proulx wrote: In the beginning systems were isolated. There was no net. Then UUCP brought light unto the darkness. This was called USENET and we saw I thought that Unix-Unix cp was for, well, copying files, of which Usenet files were only a subset? UUCP

Re: setting hardware clock from NIST

2003-11-05 Thread David Z Maze
[EMAIL PROTECTED] (Haines Brown) writes: I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w It's almost certainly better to find a local time server and not hammer on the NIST's; I'd also use ntp (ntp-simple package) to keep your clock

Re: setting hardware clock from NIST

2003-11-05 Thread Hugo Vanwoerkom
ScruLoose wrote: On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: uhm... apropos clock on my box returns clock (3)- Determine processor time clock (8)- query and set the hardware clock (RTC) hwclock (8) - query and set the hardware clock

Re: setting hardware clock from NIST

2003-11-05 Thread Haines Brown
From: David Z Maze [EMAIL PROTECTED] [EMAIL PROTECTED] (Haines Brown) writes: I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w It's almost certainly better to find a local time server and not hammer on the NIST's; I'd also

Re: setting hardware clock from NIST

2003-11-05 Thread Nate Duehr
hwclock Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock

Re: setting hardware clock from NIST

2003-11-05 Thread Kirk Strauser
At 2003-11-05T02:18:06Z, Roberto Sanchez [EMAIL PROTECTED] writes: I use the ntp and ntp-simple packages. These are the public time servers I use in /etc/ntp.conf: server ntp2.usno.navy.mil server ntp-1.vt.edu server ntp-2.vt.edu Don't do that. Besides putting a load on the precious

Re: setting hardware clock from NIST

2003-11-05 Thread John Hasler
The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Re: setting hardware clock from NIST

2003-11-05 Thread Roberto Sanchez
Kirk Strauser wrote: At 2003-11-05T02:18:06Z, Roberto Sanchez [EMAIL PROTECTED] writes: I use the ntp and ntp-simple packages. These are the public time servers I use in /etc/ntp.conf: server ntp2.usno.navy.mil server ntp-1.vt.edu server ntp-2.vt.edu Don't do that. Besides putting a load on

Re: setting hardware clock from NIST

2003-11-05 Thread Roberto Sanchez
John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers, they sent me instructions on how to setup news access. I had to explicitly

Re: setting hardware clock from NIST

2003-11-05 Thread Kirk Strauser
At 2003-11-06T02:18:09Z, Roberto Sanchez [EMAIL PROTECTED] writes: I already consulted that list. My home is in Orlando, FL :-) I only got an @yahoo.es account... Gotcha. I saw the .es and, well, you can guess. But you still shouldn't use ntp2.usno.navy.mil; every little shareware time

Re: setting hardware clock from NIST

2003-11-05 Thread John Hasler
Don't _ask_ your ISP about timeservers: their first line support is just about guaranteed to be clueless. Just stick the nameserver IP numbers in the Chrony or Ntp config file and try them. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email

Re: setting hardware clock from NIST

2003-11-05 Thread Ron Johnson
On Wed, 2003-11-05 at 20:20, Roberto Sanchez wrote: John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers, they sent me

Re: setting hardware clock from NIST

2003-11-05 Thread Roberto Sanchez
Ron Johnson wrote: On Wed, 2003-11-05 at 20:20, Roberto Sanchez wrote: John Hasler wrote: The first place to look for time servers is your ISP. ISPs often run time service on their nameservers. Try them. I tried my ISP first. When I sent tech support an email asking about the NTP servers,

NTP packages (was: setting hardware clock from NIST)

2003-11-05 Thread moseley
Can someone summarize the different ntp packages? For example what to run on a server vs. on an internal NAT'ed workstation. Or what is best for a dialup ADSL connection vs. full-time connection. Do all packages provied a daemon? I'm using both chrony and ntp on various machines, and it

setting hardware clock from NIST

2003-11-04 Thread Haines Brown
I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock (or at least the system

Re: setting hardware clock from NIST

2003-11-04 Thread Roberto Sanchez
Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and that seems to work fine to set the system clock (or at

Re: setting hardware clock from NIST

2003-11-04 Thread ScruLoose
On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: I'm a RedHat refugee, and sometimes I can just transfer things to debian, and sometimes not. I have an executable script, time.rc which has: #! /bin/bash rdate -s time-b.nist.gov clock -w I installed rdate, and

Re: setting hardware clock from NIST

2003-11-04 Thread Laurence J. Lane
On Tue, Nov 04, 2003 at 09:04:58PM -0500, Haines Brown wrote: So my first question is, what is debian's equivalent to clock. All it did, with the -w option, was to set the hardware clock from the system clock. I presume the former is GMT, and so there is a time offset invoved. hwclock -w