Re: NTP packages (was: setting hardware clock from NIST)
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 external stratum 2 server that I use to get the time. The other machines, which are NATed by the first machine, point to the first machine and get their time reference from it. Chrony is a wrapper around ntp, and some code that keeps track of whether your computer's internal clock runs fast or slow compared to the ntp server's clock, and adjusts the rate to match the ntp server's rate. All other options (except pure ntp) are wrappers around ntp. Some may also adjust the rate of your local clock as well. Depending on your tastes, one or another may be more to your liking. I like chrony because, once I got it installed and configured, it is invisible to me (except that my computers and my 'SkyScan Atomic Clock' always agree.) 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 seems as if they both provide ntp network service (via netstat and lsof), but seems like I can run this nptdate -d machine running ntp but this fails ntpdate -d machine running chronyd Probably the chronyd machine is configured to *not* serve time to other hosts. Check the 'allow' statements in /etc/chrony/chrony.conf But I'm not sure why one works and not the other. Also, what uses the time and daytime services provided via inetd? I don't know about inetd time. HTH -- Paul E Condon [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NTP packages (was: setting hardware clock from NIST)
[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 isolated systems did not know the time of other systems. Then as it became useful and required to keep the time of systems reasonably close people starting setting the time with random programs and scripts. People were ignorant of the problems of stepping the time on a system would step the time on a running system with 'rdate' and other commands. But this can cause problems. The easiest to visualize is that cron might not run a task or might run a task twice depending on the step. Then smarter programs were developed such sn xntpd which would squeeze and expand cpu cycles within a second so that every second was seen by the system. This pleased the system admins and it was good. After many years of use xntpd became the standard tool and the x for experimental was dropped from the name. It is now ntpd and the defacto standard program. Later in time others were embracing the way of the open source and proverb that there are many ways to do things. Programs like chrony emerged as a competitor to the ntpd program. Not having ever used it because ntpd does such a good job for me even on my sometimes connected systems like my laptop I can't say why people like chrony. But their users tend to be fanatical about it. Best to stay out of the way lest the thread length soon becomes greater than 100! For example what to run on a server vs. on an internal NAT'ed workstation. All unix hosts are servers whether they are behind a NAT firewall or not. I imagine that it does not matter which implementation of the service you use as long as you use a good one. How you configure them matters. The firewall would prevent you from peering the two systems. But the host behind the firewall could use the host outside as a server. In /etc/ntp.conf speak a host shares with its 'peer' hosts and UDP traffic is bidirectional. But a client just polls and pulls from a 'server'. Or what is best for a dialup ADSL connection vs. full-time connection. I use ntpd for both. Works great. I use ntpd on my laptop too. I'm using both chrony and ntp on various machines, and it seems as if they both provide ntp network service (via netstat and lsof), but seems like I can run this nptdate -d machine running ntp but this fails ntpdate -d machine running chronyd But I'm not sure why one works and not the other. Let me hazard a guess that chrony is not a full implemention. It is the newcomer to the block and so may not have gotten around to implementing everything. But again I have not used it so this is complete supposition on my part. It is just as possible that ntpdate is using nonstandard extensions only provided by ntpd. Also, what uses the time and daytime services provided via inetd? Today? Nothing of which I am aware. Twenty years ago? Diagnostic scripts written by local admins to debug their clocks. Actually even today one of the local admins at my site has a big time pinger that uses that to make sure the host is up and talking. You can ping a host that is hung because the network card or driver may be able to respond regardless of the state of the machine. But time goes through inetd and so it shows that the machine has at least a little higher order brain function working. And if the time is significantly off from what is expected then you know the system is sick and in need of some tlc to repair it. You can pretty safely disable those today. People tend to leave them in place for historical reasons. They don't hurt anything and so there they are. Every so often someone starts a discussion suggesting that any open service is a security hole and suggests that these should be off. But there are no known exploits. (Note to the list: Let's not go down the rat hole of how to exploit these, we have heard them all before.) Bob pgp0.pgp Description: PGP signature
UUCP Usenet (was Re: NTP packages (was: setting hardware clock from NIST))
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 Unix-Unix cp was for, well, copying files, of which Usenet files were only a subset? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA I have created a government of whirled peas... Maharishi Mahesh Yogi, 12-May-2002, CNN, Larry King Live -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NTP packages (was: setting hardware clock from NIST)
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 thread, the OP's problem with Ntpdate is most likely due to the machine from which he is trying to run it not being authorized to connect to Chrony. If that is not the case please file a bug report. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NTP packages (was: setting hardware clock from NIST)
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? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
[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. I normally don't reboot for months at a time, and so need to sync clocks with cron. I'll kill the symlink in /etc/rc2.d. I assume that /usr/sbin/ntpd is the executable that I should symlink in /etc/cron.daily. 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 up a cron job. In reading the doc, I see that ntpq, run without argument, is a way to do a simple test of ntp functionality. However, that does not seem to be part of the ntp-simple package, nor is it itself a package. Have you used ntpq, and if so, how? It's in the base ntp package, which is suggested by ntp-simple. For looking at my own ntp daemon, 'ntpdc -s' will give you a short summary of what other time daemons you're talking to, and 'ntptrace' will show the synchronization chain from yourself to a stratum-1 time server. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 up a cron job. Thank you very much, David. Knowing that installation of ntp-simple automatically sets up the clock syncronization makes things very simple. Also, the 6-sec error I noted will then disappear in time. In reading the doc, I see that ntpq, run without argument, is a way to do a simple test of ntp functionality. However, that does not seem to be part of the ntp-simple package, nor is it itself a package. Have you used ntpq, and if so, how? It's in the base ntp package, which is suggested by ntp-simple. For looking at my own ntp daemon, 'ntpdc -s' will give you a short summary of what other time daemons you're talking to, and 'ntptrace' will show the synchronization chain from yourself to a stratum-1 time server. I installed ntp (which I didn't realize I had failed to do). and ran the following. Don't know if it means ntp-simple not running: # ntpdc -s ***Server reports data not found # ntptrace localhost: stratum 16, offset 0.11, sync distance 0.31587 0.0.0.0: *Not Syncronized* The first puzzles me, and sounds like there's no connection with the server. The second sounds like the time is retrieved, but there has not been sufficient time to achieve complete sync. Haines -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: UUCP Usenet (was Re: NTP packages (was: setting hardware clock from NIST))
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 enabled mail and news which IMNHO were the foundation for USENET. The underlying foundation to both mail and news is to be able to copy files between systems. UUCP was a reasonable networking technology back in the day. If you can copy data then you can implement anything[1]. Until you start networking you don't really care what time systems are keeping. How many people ever reset the time on their watch while getting away from it all camping? It is only in interaction that good time keeping was important. How many times do you see people post messages here with bad system times and the comments that produces from the readers? USENET provided a way for people to flame^Winteract with others. But of course it was only part of it. Bob [1] http://www.faqs.org/rfcs/rfc2549.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
[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 up-to-date while the system is running. See http://www.ntp.org/ for more information, and contact your ISP to see if they have their own time server. At any rate, on my system, the hardware clock is automatically updated from the system clock at boot and shutdown time, by /etc/init.d/hwclock.sh in the util-linux package. So if you installed and configured NTP, you'd get the same effect as this script. Second, where to put it? I placed a copy of my time.rc into /etc/init.d, and then created a symlink to it in /etc/rc2.d so that the hardware clock is reset on boot, and also in /etc/cron.daily, so that the clocks are reset daily according to NIST. Will this work; is there a better arrangement? That setup is probably fine, though I'd do either a cron script or an init.d script, not both (if your machine spends a lot of time shut down, anacron can run delayed cron jobs at boot time). If you do want an init script, I'd also make it more policy-compliant; try working from /etc/init.d/skeleton. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 (RTC) ... among others. Doesn't look like it's a RedHat thing. ... Will this work; is there a better arrangement? I don't know whether it's 'better', but I like chrony Yep! Second that. I also use chrony and I like the hands-on approach of it. So I wrote a wminet that talks to chrony and keeps showing what chrony has done. H. for keeping the time. It may be a bit of overkill, but it sure does a good job. Cheers! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 use ntp (ntp-simple package) to keep your clock up-to-date while the system is running. Yes, quite something. It's been years since I've looked into this, and it is now much more established. For one thing, if I recall correctly, there were only 2-3 servers. Following your recommendation, I got the address of a local time server and also installed ntp-simple. That setup is probably fine, though I'd do either a cron script or an init.d script, not both (if your machine spends a lot of time shut down, anacron can run delayed cron jobs at boot time). If you do want an init script, I'd also make it more policy-compliant; try working from /etc/init.d/skeleton. Thanks for the advice. I normally don't reboot for months at a time, and so need to sync clocks with cron. I'll kill the symlink in /etc/rc2.d. I assume that /usr/sbin/ntpd is the executable that I should symlink in /etc/cron.daily. In reading the doc, I see that ntpq, run without argument, is a way to do a simple test of ntp functionality. However, that does not seem to be part of the ntp-simple package, nor is it itself a package. Have you used ntpq, and if so, how? Haines -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 (or at least the system clock jumped to 6 sec from what my local telco says the time is). However, the clock utility, which writes system time to the hardware clock is native to RedHat. 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. Second, where to put it? I placed a copy of my time.rc into /etc/init.d, and then created a symlink to it in /etc/rc2.d so that the hardware clock is reset on boot, and also in /etc/cron.daily, so that the clocks are reset daily according to NIST. Will this work; is there a better arrangement? Haines Brown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 stratum-1 servers and stratum-2 servers on the other side of the Big Pond, look at http://www.eecis.udel.edu/~mills/ntp/clock2a.html to find some servers closer to home. The backbone will be happier and your clock will be more accurate. -- Kirk Strauser In Googlis non est, ergo non est. pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 PROTECTED]
Re: setting hardware clock from NIST
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 the precious stratum-1 servers and stratum-2 servers on the other side of the Big Pond, look at http://www.eecis.udel.edu/~mills/ntp/clock2a.html to find some servers closer to home. The backbone will be happier and your clock will be more accurate. I already consulted that list. My home is in Orlando, FL :-) I only got an @yahoo.es account becuase they 6MB storage (versus 4MB for regular @yahoo.com) and still offer free POP3 access (which costs money for an @yahoo.com account). -Roberto pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 spell network time protocol. Yup, they are very clueful. -Roberto pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 utility syncs against those poor machines by default. -- Kirk Strauser In Googlis non est, ergo non est. pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 instructions on how to setup news access. I had to explicitly spell network time protocol. Yup, they are very clueful. Try this: traceroute ntp.yourisp I was pleasantly surprised to find that my ISP has one at ntp.cox.net. P.S. - mtr is much better than traceroute. $ apt-cache show mtr Package: mtr Priority: extra Section: net Installed-Size: 152 Maintainer: Robert Woodcock [EMAIL PROTECTED] Architecture: i386 Version: 0.54-1 Replaces: mtr-tiny Depends: libc6 (= 2.3.1-1), libglib1.2 (= 1.2.0), libgtk1.2 (= 1.2.10-4), libncurses5 (= 5.3.20021109-1), xlibs ( 4.1.0) Conflicts: suidmanager ( 0.50), mtr-tiny Filename: pool/main/m/mtr/mtr_0.54-1_i386.deb Size: 42098 MD5sum: 76bf4c099a4fd45aaa27d13711ad1f41 Description: Full screen ncurses and X11 traceroute tool mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool. . As mtr starts, it investigates the network connection between the host mtr runs on and a user-specified destination host. After it determines the address of each network hop between the machines, it sends a sequence ICMP ECHO requests to each one to determine the quality of the link to each machine. As it does this, it prints running statistics about each machine. -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA Those who would give up essential Liberty to purchase a little temporary safety, deserve neither Liberty nor safety. or something like that Ben Franklin, maybe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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, they sent me instructions on how to setup news access. I had to explicitly spell network time protocol. Yup, they are very clueful. Try this: traceroute ntp.yourisp I was pleasantly surprised to find that my ISP has one at ntp.cox.net. A simple ping of ntp.ISP showed the machine as being there, and it just a CNAME for the nameserver. I guess first line tech support really is clueless :-) -Roberto pgp0.pgp Description: PGP signature
NTP packages (was: setting hardware clock from NIST)
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 seems as if they both provide ntp network service (via netstat and lsof), but seems like I can run this nptdate -d machine running ntp but this fails ntpdate -d machine running chronyd But I'm not sure why one works and not the other. Also, what uses the time and daytime services provided via inetd? -- Bill Moseley [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
setting hardware clock from NIST
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 clock jumped to 6 sec from what my local telco says the time is). However, the clock utility, which writes system time to the hardware clock is native to RedHat. 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. Second, where to put it? I placed a copy of my time.rc into /etc/init.d, and then created a symlink to it in /etc/rc2.d so that the hardware clock is reset on boot, and also in /etc/cron.daily, so that the clocks are reset daily according to NIST. Will this work; is there a better arrangement? Haines Brown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: setting hardware clock from NIST
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 least the system clock jumped to 6 sec from what my local telco says the time is). However, the clock utility, which writes system time to the hardware clock is native to RedHat. 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. Second, where to put it? I placed a copy of my time.rc into /etc/init.d, and then created a symlink to it in /etc/rc2.d so that the hardware clock is reset on boot, and also in /etc/cron.daily, so that the clocks are reset daily according to NIST. Will this work; is there a better arrangement? Haines Brown 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 HTH, -Roberto pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 that seems to work fine to set the system clock (or at least the system clock jumped to 6 sec from what my local telco says the time is). However, the clock utility, which writes system time to the hardware clock is native to RedHat. 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 (RTC) ... among others. Doesn't look like it's a RedHat thing. ... Will this work; is there a better arrangement? I don't know whether it's 'better', but I like chrony for keeping the time. It may be a bit of overkill, but it sure does a good job. Cheers! -- ,-. -ScruLoose- | WARNING: Contains Language! Please do not | - Neil Gaiman reply off-list. | `-' pgp0.pgp Description: PGP signature
Re: setting hardware clock from NIST
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 Second, where to put it? I placed a copy of my time.rc into /etc/init.d, and then created a symlink to it in /etc/rc2.d so that the hardware clock is reset on boot, and also in /etc/cron.daily, so that the clocks are reset daily according to NIST. Will this work; is there a better arrangement? Anywhere after the network device initialization should do. The ntpdate package may interest you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
