Re: ntpdate: Can't find host 0.debian.pool.ntp.org

staticsafe staticsafe.ca> writes: > > On 4/17/2014 20:43, Amit wrote: > > Name or service not known (-2) > > Sounds like you have/had DNS issues. Perhaps the resolver(s) in > /etc/resolv.conf were unresponsive? > Thanks. I think I may have found the issue. ntpdate is being called twice. Fir

Re: ntpdate: Can't find host 0.debian.pool.ntp.org

Kumar Appaiah alumni.iitm.ac.in> writes: [snip] > > > Apr 17 17:36:22 test ntpdate[709]: Can't find host 2.debian.pool.ntp.org: > > Name or service not known (-2) > > Apr 17 17:36:22 test ntpdate[709]: no servers can be used, exiting > > Apr 17 17:36:45 test ntpdate[1148]: adjust time server 6

Re: ntpdate: Can't find host 0.debian.pool.ntp.org

On 4/17/2014 20:43, Amit wrote: > Name or service not known (-2) Sounds like you have/had DNS issues. Perhaps the resolver(s) in /etc/resolv.conf were unresponsive? -- staticsafe https://asininetech.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsub

Re: ntpdate: Can't find host 0.debian.pool.ntp.org

On Fri, Apr 18, 2014 at 12:43:28AM +, Amit wrote: > Have a minimal debian system and installed ntpdate. Time seems to be set > correctly but getting these messages: > > $ journalctl -b | grep ntp > Apr 17 17:36:22 test ntpdate[709]: Can't find host 0.debian.pool.ntp.org: > Name or service not

Re: Ntpdate Errors (previously posted, +)

On Thu, Jun 17, 2010 at 11:42 PM, David Baron wrote: > > [snip] > > So .. I got rid of ntpdate altogether, installed the ntp daemon instead. I > still get the error messages, now with /usr/sbin/ntpdate does not exist (of > course). So I still need to find the original cron script! > write a scrip

Re: Ntpdate Errors (previously posted, +)

On Tuesday 15 June 2010 18:42:02 David Baron wrote: > On Saturday 12 June 2010 23:02:11 David Baron wrote: > > > > I have no cron running ntpdate that I know of and there is no ntpdate > > > > entry in anacrontab. I run it in an rc.local type script on bootup. > > > > Period. This run works. > > >

Re: Ntpdate Errors (previously posted, +)

On Tue, Jun 15, 2010 at 06:42:02PM +0300, David Baron wrote: > On Saturday 12 June 2010 23:02:11 David Baron wrote: > > > > I have no cron running ntpdate that I know of and there is no ntpdate > > > > entry in anacrontab. I run it in an rc.local type script on bootup. > > > > Period. This run wor

Re: Ntpdate Errors (previously posted, +)

On Saturday 12 June 2010 23:02:11 David Baron wrote: > > > I have no cron running ntpdate that I know of and there is no ntpdate > > > entry in anacrontab. I run it in an rc.local type script on bootup. > > > Period. This run works. > > > > > > The only thing I can think of is an obsolete webmin

Re: Ntpdate Errors (previously posted, +)

> > I have no cron running ntpdate that I know of and there is no ntpdate > > entry in anacrontab. I run it in an rc.local type script on bootup. > > Period. This run works. > > > > The only thing I can think of is an obsolete webmin entry but I have not > > run webmin for ages. This simply made

Re: Ntpdate Errors (previously posted, +)

> > I have no cron running ntpdate that I know of and there is no ntpdate > > entry in anacrontab. I run it in an rc.local type script on bootup. > > Period. This run works. > > > > The only thing I can think of is an obsolete webmin entry but I have not > > run webmin for ages. This simply made

Re: Ntpdate Errors (previously posted, +)

On 06/10/2010 10:38 AM, David Baron wrote: > I get these periodically through the day: > > Cron /usr/sbin/ntpdate -s 216.200.93.8 (failed) > From: Cron Daemon > To: r...@dovidhalevi.homelinux.net > > command failed with exit status 1 Woah! Cron should NOT be running NTP. That defeats the wh

Re: Ntpdate Errors (previously posted, +)

On Thu, 10 Jun 2010 19:38:00 +0300 David Baron wrote: > I get these periodically through the day: > > Cron /usr/sbin/ntpdate -s 216.200.93.8 (failed) > From: Cron Daemon > To: r...@dovidhalevi.homelinux.net > > command failed with exit status 1 > > I have no cron running ntpdate that I kn

Re: ntpdate cron error

2010/5/14 Rob Owens : > > Not sure.  But do you think you should be running the ntp daemon instead > of using ntpdate in cron? > > -Rob I think that's indeed the way to go, yes. -- Frank Van Damme A: Because it destroys the flow of the conversation. Q: Why is it bad? A: No, it's bad. Q: Should

Re: ntpdate cron error

On Thu, May 13, 2010 at 07:28:05PM +0300, David Baron wrote: > The initial ntpdate run from /etc/init.d succeeds. > > However, as of recent upgrades or site changes, a cron run of ntpdate fails: > > Cron ... /usr/sbin/ntpdate -s 216.200.93.8 (failed) > ... > command failed with exit status 1 >

Re: ntpdate cron error

2010/5/13 David Baron : > The initial ntpdate run from /etc/init.d succeeds. > > However, as of recent upgrades or site changes, a cron run of ntpdate fails: > > Cron ... /usr/sbin/ntpdate -s 216.200.93.8 (failed) >  ... > command failed with exit status 1 > > I assume that the IP shown is not avai

Re: ntpdate[5498]: no server suitable for synchronization found

Thanks Rick. That was the problem of firewall. ~Anup - Original Message - From: "Rick Thomas" <[EMAIL PROTECTED]> To: "anup" <[EMAIL PROTECTED]> Cc: Sent: Monday, June 18, 2007 2:03 PM Subject: Re: ntpdate[5498]: no server suitable for synchronizatio

Re: ntpdate[5498]: no server suitable for synchronization found

e for synchronization found Is it necessary to access time server only on Live server in my organization or i can access it on internal network PC? - Original Message - From: "Rick Thomas" <[EMAIL PROTECTED]> To: "anup" <[EMAIL PROTECTED]> Cc: Sent: Sunday

Re: ntpdate[5498]: no server suitable for synchronization found

I assume you are in Asia. If so, run the following script and examine the output. Pick three hosts that look best and use them in place of "3.asia.pool.ntp.org". Script: cut here--- for i in 0 1 2 3 do host $i.asia.pool.ntp.org done | while read x echo

Re: ntpdate[5498]: no server suitable for synchronization found

On 06/16/07 07:35, Michael Marsh wrote: On 6/16/07, anup <[EMAIL PROTECTED]> wrote: I am trying to setup NTP client inside my network using public time server. I used " ntpdate -ud 3.asia.pool.ntp.org " it gives the following error messaage.. [...] 16 Jun 15:20:26 ntpdate[5498]: no server sui

Re: ntpdate[5498]: no server suitable for synchronization found

On 6/16/07, anup <[EMAIL PROTECTED]> wrote: I am trying to setup NTP client inside my network using public time server. I used " ntpdate -ud 3.asia.pool.ntp.org " it gives the following error messaage.. [...] 16 Jun 15:20:26 ntpdate[5498]: no server suitable for synchronization found Please h

Re: ntpdate[5498]: no server suitable for synchronization found

On Sat, Jun 16, 2007 at 03:29:33PM +0530, anup wrote: > I am trying to setup NTP client inside my network using public time server. > I used " ntpdate -ud 3.asia.pool.ntp.org " it gives the following error > messaage.. > > 202.234.64.222: Server dropped: no data Can you try a specific server? A

Re: NTPDate Broken? (SOLVED)

On Sun, Mar 11, 2007 at 03:12:29PM -0400, Rick Thomas wrote: > Based on your email address, you seem to be located in Israel. If > so, do "host il.pool.ntp.org". That will give you the IP addresses > of a small number of nearby ntp servers. Put three of them as > servers in your /etc/ntp.

Re: NTPDate Broken? (SOLVED)

On Mar 11, 2007, at 9:18 AM, David Baron wrote: On Saturday 10 March 2007, debian-user-digest- [EMAIL PROTECTED] wrote: Has anyone had a problem with the more recent ntpdate from Sid? Fix, Workaround? Cannot find suitable server. Works for me just fine with these NTP servers. I have not s

Re: NTPDate Broken?

on Sat, Mar 10, 2007 at 08:33:14PM -0800 Paul Johnson wrote: > David Baron wrote in Article <[EMAIL PROTECTED]> posted > to gmane.linux.debian.user: > > > Has anyone had a problem with the more recent ntpdate from Sid? > > Fix, Workaround? > > Have you tried using chrony instead? Try running 'nt

Re: NTPDate Broken? (SOLVED)

On Saturday 10 March 2007, [EMAIL PROTECTED] wrote: > > > Has anyone had a problem with the more recent ntpdate from Sid? > > > Fix, Workaround? > > > > > > Cannot find suitable server. > > > > Works for me just fine with these NTP servers. > > I have not seen any error about it over here. My trus

Re: NTPDate Broken?

David Baron wrote in Article <[EMAIL PROTECTED]> posted to gmane.linux.debian.user: > Has anyone had a problem with the more recent ntpdate from Sid? > Fix, Workaround? Have you tried using chrony instead? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble

Re: NTPDate Broken?

On Sat, Mar 10, 2007 at 12:59:07PM -0600, Ron Johnson wrote: > On 03/10/07 12:34, David Baron wrote: > > Has anyone had a problem with the more recent ntpdate from Sid? > > Fix, Workaround? > > > > Cannot find suitable server. > > Works for me just fine with these NTP servers. I have not seen an

Re: NTPDate Broken?

On 03/10/07 12:34, David Baron wrote: > Has anyone had a problem with the more recent ntpdate from Sid? > Fix, Workaround? > > Cannot find suitable server. Works for me just fine with these NTP servers. Occasionally, though, it fails when I have router issues. > > # The settings in this file

Re: ntpdate foibles?

On Tuesday 11 April 2006 13:02, Matus UHLAR - fantomas wrote: > On 05.04.06 18:46, David Baron wrote: > > There was a kernel bug to this effect but apparently not relevant to my > > configuration. When ntpdate cannot access a ntp server, the time gets > > placed two (three with daylight time) hours

Re: ntpdate foibles?

On 05.04.06 18:46, David Baron wrote: > There was a kernel bug to this effect but apparently not relevant to my > configuration. When ntpdate cannot access a ntp server, the time gets > placed two (three with daylight time) hours fast. I am two hours later > than Grenwich. It does not matter if the

Re: ntpdate foibles?

On Wednesday 05 April 2006 08:46, David Baron wrote: > If I keep trying until it succedes, then time gets set correctly. Why use ntpdate when chrony synchronizes your clock via NT Pand isn't a pain in the ass about it? -- Paul Johnson Email and IM (XMPP & Google Talk): [EMAIL PROTECTED] Jabber:

Re: ntpdate -> configuration

On Tue, 2005-12-27 at 22:55 +0100, Michael Przysucha wrote: > I have a very unstable hw-clock and need to synchronize it every apx. 60 > minutes to avoid differences of more than 20 > sec. The given server (192.53.103.103) is up and running a ntp-service, > operated by the German PTB (compareab

Re: ntpdate -> configuration

Michael Przysucha writes: > I have a very unstable hw-clock and need to synchronize it every apx. 60 > minutes to avoid differences of more than 20 sec. I suggest that you install either chrony or ntp-simple. They will take care of your clock for you. -- John Hasler -- To UNSUBSCRIBE, email t

RE: ntpdate inside Debian vservers

ain. Regards, Rabbie. -Original Message- From: Maurits van Rees [mailto:[EMAIL PROTECTED] Sent: Thursday, October 27, 2005 5:31 AM To: debian-user@lists.debian.org Subject: Re: ntpdate inside Debian vservers On Thu, Oct 27, 2005 at 02:42:31AM +1000, Rabbie Zalaf wrote: > I have a few

Re: ntpdate inside Debian vservers

On Thu, Oct 27, 2005 at 02:42:31AM +1000, Rabbie Zalaf wrote: > I have a few vservers running on my box and all of the vservers times are > off (way off I might add). I have a virtual host with Bytemark. Maybe what they have to say about setting the time helps you: http://www.bytemark.co.uk/supp

Re: ntpdate & script to update host at random time

On Fri, Jun 03, 2005 at 11:36:41AM -0400, jmr_071769 wrote: > hello again with a debian question. > > i'd like to be able to have a few machines 'apt-get update' themselves > at a random time near/around midnight. how can i go about this with > another easy script? > I almost forgot, in my previo

Re: ntpdate & script to update host at random time

On Fri, Jun 03, 2005 at 11:36:41AM -0400, jmr_071769 wrote: > hello again with a debian question. > > i'd like to be able to have a few machines 'apt-get update' themselves > at a random time near/around midnight. how can i go about this with > another easy script? > A random time around midnight

Re: ntpdate & script to update host at random time

jmr_071769 wrote: hello again with a debian question. i'd like to be able to have a few machines 'apt-get update' themselves at a random time near/around midnight. how can i go about this with another easy script? tia! -jeff See my message in debian-user archives with the subject "My local

Re: ntpdate & script to update host at random time

jmr_071769 wrote: > hello again with a debian question. > > i'd like to be able to have a few machines 'apt-get update' themselves > at a random time near/around midnight. how can i go about this with > another easy script? > > tia! > > -jeff > please disregard the ntpdate comment in the subje

Re: ntpdate doesn't fix bogus times!

On Thu, 08 Apr 2004, Pigeon wrote: > On Wed, Apr 07, 2004 at 08:30:29PM -0700, William Ballard wrote: > > On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote: > > > IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off > > > by too much. I think by default it is

Re: ntpdate doesn't fix bogus times!

On Wed, Apr 07, 2004 at 08:30:29PM -0700, William Ballard wrote: > On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote: > > IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off > > by too much. I think by default it is 1 hour (3600 sec) for all three of > > them

Re: ntpdate doesn't fix bogus times!

On Wed, Apr 07, 2004 at 11:47:50PM -0600, Bob Proulx wrote: > Best not to run ntpdate to step the clock while ntpd is running or > confusion would result. So stop ntpd first and start it again > afterward. ...in fact, you have to stop ntpd, or else ntpdate won't work. -- Pigeon Be kind to pige

Re: Chrony vs ntpd (was Re: ntpdate doesn't fix bogus times!)

On Thu, 08 Apr 2004, Kirk Strauser wrote: > At 2004-04-08T03:04:46Z, Christian Schnobrich <[EMAIL PROTECTED]> writes: > > Oh, and... everybody suggests chrony as a far superior and more stable > > solution than ntpd. For certain situations, yes. Chrony is much better for high latency, inconstant

Re: Chrony vs ntpd (was Re: ntpdate doesn't fix bogus times!)

* Kirk Strauser <[EMAIL PROTECTED]> [040408 09:05]: > > I occasionally hear someone say that chrony is better than ntpd, but > I've never heard the reasons why. I tried setting up ntp and found it difficult, but tried setting up chrony and found it easy. Since I'm just running a few boxes at h

Chrony vs ntpd (was Re: ntpdate doesn't fix bogus times!)

At 2004-04-08T03:04:46Z, Christian Schnobrich <[EMAIL PROTECTED]> writes: > Oh, and... everybody suggests chrony as a far superior and more stable > solution than ntpd. More stable? In what way? Not once in the years that I've used ntpd have I ever had problems with it. I occasionally hear som

Re: ntpdate doesn't fix bogus times!

Chris Horn wrote: > cc: me on your reply, as I'm not subscribed)! > Running '/etc/init.d/ntpdate start' does not fix the problem. What do the logs say in /var/log/syslog? I suspect you have a firewall in the way. Try running ntpdate interactively. /etc/init.d/ntp stop# or /etc/init.d/ntp

Re: ntpdate doesn't fix bogus times!

On Thu, Apr 08, 2004 at 05:04:46AM +0200, Christian Schnobrich wrote: > IIRC, ntpdate (and ntpd and chrony) will not set your clock if it is off > by too much. I think by default it is 1 hour (3600 sec) for all three of > them. ntpdate just adjusted my clock which was off by 3602 seconds 7 Apr 1

Re: ntpdate doesn't fix bogus times!

On Thursday 08 April 2004 03:04 am, Christian Schnobrich wrote: >I can merely point you to the (quite exhaustive) documentation you get >when installing ntp-doc. As quick fix, you may manually set the time to >something that's reasonably close and re-run ntpdate. Sorry, this just doesn't work. A

Re: ntpdate doesn't fix bogus times!

On Don, 2004-04-08 at 04:20, Chris Horn wrote: > Okay, I'm completely lost on this one. I have one box that can't tell time > and I don't know what's the matter with it. > > when UTC is around Thu Apr 8 02:16:20 UTC 2004, this machine reports: > > # date -u && date > Wed Apr 7 22:16:37 UTC 200

Re: ntpdate doesn't fix bogus times!

On Thursday 08 April 2004 02:20 am, Chris Horn wrote: >Okay, I'm completely lost on this one. I have one box that can't tell time >and I don't know what's the matter with it. > >when UTC is around Thu Apr 8 02:16:20 UTC 2004, this machine reports: > ># date -u && date >Wed Apr 7 22:16:37 UTC 200

Re: ntpdate leap year

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 03, 2004 at 07:02:15PM -0700, Nate Duehr wrote: > >Surely "ntp-simple" is a "real" NTP client. I mean, it's *the* NTP > >software package (i.e., the official reference implementation of the > >NTPv4 protocol). The "-simple" part just mean

Re: ntpdate leap year

On Mar 3, 2004, at 5:12 PM, Kevin Buhr wrote: Paul Johnson <[EMAIL PROTECTED]> writes: Get a real NTP client? chrony didn't screw up... Surely "ntp-simple" is a "real" NTP client. I mean, it's *the* NTP software package (i.e., the official reference implementation of the NTPv4 protocol). The "-

Re: ntpdate leap year

Paul Johnson <[EMAIL PROTECTED]> writes: > > Get a real NTP client? chrony didn't screw up... Surely "ntp-simple" is a "real" NTP client. I mean, it's *the* NTP software package (i.e., the official reference implementation of the NTPv4 protocol). The "-simple" part just means it doesn't include

Re: ntpdate leap year

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 01, 2004 at 06:39:53PM -0900, Greg Madden wrote: > I use ntp-simpl. This is a leap year, 29 days in February, but ntp is > short by one day. I can adjust the date manually but when ntp runs it > sets me back a day. Is there away to tell n

Re: ntpdate leap year

Greg Madden <[EMAIL PROTECTED]> writes: > > I use ntp-simpl. This is a leap year, 29 days in February, but ntp is > short by one day. I can adjust the date manually but when ntp runs it > sets me back a day. Is there away to tell ntp about leap years ? First, not to be a wiseass, but you might w

Re: ntpdate leap year

Greg Madden wrote: I use ntp-simpl. This is a leap year, 29 days in February, but ntp is short by one day. I can adjust the date manually but when ntp runs it sets me back a day. Is there away to tell ntp about leap years ? I also run ntp-simple, and it got the 29th day with no problem. Perhaps you

Re: ntpdate from cron -- DON'T DO THAT!

On Sun, Dec 29, 2002 at 02:18:18AM -0800, alan brown wrote: > I may be wrong but I think it's more generic than burning CD's. I've > heard it's related to SCSI drives. Just hearsay. Throw it into the > mix... On the victim machine I'm using IDE drives with SCSI emulation for the CD writer, no a

Re: ntpdate tip -- hmm? [NEW TOPIC]

On Sat, Dec 28, 2002 at 11:28:26AM -0700, Bob Proulx wrote: > > On Fri, 2002-12-27 at 11:39, will trillich wrote: > > > > DEBIAN NEWBIE TIP #59 from Will Trillich <[EMAIL PROTECTED]> > > > > Wanting to SYNCHRONIZE YOUR SYSTEM CLOCK periodically? If you > > > > apt-get install ntpdate ntp-do

RE: ntpdate from cron -- DON'T DO THAT!

002 1:33 AM To: Bill Moseley Cc: [EMAIL PROTECTED] Subject: Re: ntpdate from cron -- DON'T DO THAT! On Sat, Dec 21, 2002 at 04:14:32PM -0800, Bill Moseley wrote: > ... > > The other possibility, brought up by someone on this list, is that that > machine is used for burning CDs and

Re: ntpdate from cron -- DON'T DO THAT!

On Sat, Dec 21, 2002 at 04:14:32PM -0800, Bill Moseley wrote: > ... > > The other possibility, brought up by someone on this list, is that that > machine is used for burning CDs and that may cause the clock to get slow. > I have not check this, though. I'll second that warning, as I saw just that

Re: ntpdate tip -- hmm? [NEW TOPIC]

On Sat, Dec 28, 2002 at 11:28:26AM -0700, Bob Proulx wrote: ... > However, the pointer to rtfm is probably too much for most newbies. > It would be great if ntpdate and ntp-simple both offered to do the > very simple configuration of using the existing DNS servers as NTP > servers and having the de

Re: ntpdate tip -- hmm? [NEW TOPIC]

John Hasler <[EMAIL PROTECTED]> [2002-12-28 12:51:12 -0600]: > Bob Proulx writes: > > It would be great if ntpdate and ntp-simple both offered to do the very > > simple configuration of using the existing DNS servers as NTP servers > > I'm considering having chrony do this. How common is it for a

Re: ntpdate tip -- hmm? [NEW TOPIC]

On 28 Dec 2002, John Hasler wrote: > Bob Proulx writes: > > It would be great if ntpdate and ntp-simple both offered to do the very > > simple configuration of using the existing DNS servers as NTP servers > > I'm considering having chrony do this. How common is it for an ISPs dns > servers to p

Re: ntpdate tip -- hmm? [NEW TOPIC]

Rob Weir writes: > Is there any reason to not use chrony on a leaf system, since it seems to > do the funky slew dance by default, as well as neatly integrating into > ppp's up and down scripts? No reason I can think of, but I _am_ biased. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Ho

Re: ntpdate tip -- hmm? [NEW TOPIC]

Bob Proulx writes: > It would be great if ntpdate and ntp-simple both offered to do the very > simple configuration of using the existing DNS servers as NTP servers I'm considering having chrony do this. How common is it for an ISPs dns servers to provide ntp service? Mine didn't a few years ago

Re: ntpdate tip -- hmm? [NEW TOPIC]

Mark L. Kahnt <[EMAIL PROTECTED]> [2002-12-27 12:52:29 -0500]: > On Fri, 2002-12-27 at 11:39, will trillich wrote: > > > DEBIAN NEWBIE TIP #59 from Will Trillich <[EMAIL PROTECTED]> > > > Wanting to SYNCHRONIZE YOUR SYSTEM CLOCK periodically? If you > > > apt-get install ntpdate ntp-doc > > > the

Re: ntpdate from cron -- DON'T DO THAT!

John Hasler <[EMAIL PROTECTED]> [2002-12-23 08:03:45 -0600]: > > I think you'd stump the frontline staff at any isp with this one, and > > it's not really important enough to email thier NOC about in the end... > > Of course I'd stump the frontline staff of my ISP with questions about time > serve

Re: ntpdate from cron -- DON'T DO THAT!

At 2002-12-28T15:08:38Z, Laura Conrad <[EMAIL PROTECTED]> writes: > No, anyone who sells disk space should have a time server. I don't care > whether my time is exactly in sync with the ISP who provides my internet > connection, but I want to have the same time as the webserver provider who > se

Re: ntpdate from cron -- DON'T DO THAT!

> "Michael" == Michael D Schleif <[EMAIL PROTECTED]> writes: Michael> imho, all isp's ought to be required to *have* time servers . . . No, anyone who sells disk space should have a time server. I don't care whether my time is exactly in sync with the ISP who provides my internet connect

Re: ntpdate tip -- hmm? [NEW TOPIC]

On Fri, Dec 27, 2002 at 12:52:29PM -0500, Mark L. Kahnt wrote: > On Fri, 2002-12-27 at 11:39, will trillich wrote: > > On Fri, Dec 27, 2002 at 10:17:01AM -0600, will trillich wrote: > > > -- > > > I use Debian/GNU Linux version 2.2; > > > Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 un

Re: ntpdate tip -- hmm? [NEW TOPIC]

On Fri, 2002-12-27 at 11:39, will trillich wrote: > On Fri, Dec 27, 2002 at 10:17:01AM -0600, will trillich wrote: > > -- > > I use Debian/GNU Linux version 2.2; > > Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown > > > > DEBIAN NEWBIE TIP #59 from Will Trillich <[EMAIL PROTECTE

Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

> I thought chronyd did not implement all of the time protocol RFC and had > fewer device interfaces for time sources. AFAIK the only thing missing from Chrony is support for things like atomic clocks. > So, maybe in that sense ntpd is "technically the best"? If you are running a stratum one ser

Re: ntpdate from cron -- DON'T DO THAT!

On Mon, Dec 23, 2002 at 04:08:34PM +0100, Chris Niekel wrote: > But indeed, time is of no critical importance to me, so maybe I should > just remove a few of the servers. If you already have them listed, there's no real reason to remove them, as it'll maintain reliability if the timeservers go out

Re: ntpdate from cron -- DON'T DO THAT!

On Mon, Dec 23, 2002 at 08:09:41AM -0600, John Hasler wrote: > Chris Niekel writes: > > The NTP-docs mention that you should not use only one server, but more. > > Is reliable time service of critical importance to you? Most systems can > go for days without contacting a timeserver and suffer no

Re: ntpdate from cron -- DON'T DO THAT!

Chris Niekel writes: > The NTP-docs mention that you should not use only one server, but more. Is reliable time service of critical importance to you? Most systems can go for days without contacting a timeserver and suffer no harm. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hil

Re: ntpdate from cron -- DON'T DO THAT!

Paul Johnson writes: > [A UBR is] part of a cable network. Then my ISP doesn't have one. > I think you'd stump the frontline staff at any isp with this one, and > it's not really important enough to email thier NOC about in the end... Of course I'd stump the frontline staff of my ISP with questi

Re: ntpdate from cron -- DON'T DO THAT!

On Sat, Dec 21, 2002 at 07:01:41PM -0600, John Hasler wrote: > And that higher stratum server should be that of your ISP, if possible. > IMHO all ISPs should make time servers available to their customers. The NTP-docs mention that you should not use only one server, but more. I've added a few oth

Re: ntpdate from cron -- DON'T DO THAT!

On Sun, Dec 22, 2002 at 08:05:55AM -0600, John Hasler wrote: > > The local UBR should do that shouldn't it? > > What's a UBR? Back when I was working for @Home, I knew this. It's part of a cable network. > My ISP certainly doesn't, and I doubt that I could contact with anyone > there who knows

Re: ntpdate from cron -- DON'T DO THAT!

I wrote: > What's a UBR? Richard Kimber writes: > The local router that acts as your gateway. No ntp service available there. -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact

Re: ntpdate from cron -- DON'T DO THAT!

On 22 Dec 2002 08:05:55 -0600 John Hasler <[EMAIL PROTECTED]> wrote: > What's a UBR? > > > I'm pretty sure it does with the NTL cable system I'm on. > > My ISP certainly doesn't, and I doubt that I could contact with anyone > there who knows what a time server is. The local router that acts as

Re: ntpdate from cron -- DON'T DO THAT! - more

Bob writes: > How does rdate compare to chrony and nptd? Rdate uses the RFC868 protocol while Chrony and Ntp use the RFC1305 (NTP) protocol. Look here for a comparison. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwoo

Re: ntpdate from cron -- DON'T DO THAT! - more

How does rdate compare to chrony and nptd? Regards, Bob -- _ |_) _ |_Robert D. Hilliard<[EMAIL PROTECTED]> |_) (_) |_) 1294 S.W. Seagull Way <[EMAIL PROTECTED]> Palm City, FL 34990 USA GPG Key ID: 390D6559

Re: ntpdate from cron -- DON'T DO THAT!

I wrote: > And that higher stratum server should be that of your ISP, if possible. > IMHO all ISPs should make time servers available to their customers. Richard Kimber writes: > The local UBR should do that shouldn't it? What's a UBR? > I'm pretty sure it does with the NTL cable system I'm on.

Re: ntpdate from cron -- DON'T DO THAT!

I wrote: > Then your clients should have been connecting to the ntp daemons on your > servers, so there should have been no impact on the public servers. Antoine Jacoutot writes: > All my clients did ntpdate to local servers, and the servers (which were > using ntpd) are connecting to public serve

Re: ntpdate from cron -- DON'T DO THAT!

On 21 Dec 2002 19:01:41 -0600 John Hasler <[EMAIL PROTECTED]> wrote: > And that higher stratum server should be that of your ISP, if possible. > IMHO all ISPs should make time servers available to their customers. The local UBR should do that shouldn't it? I'm pretty sure it does with the NTL ca

Re: ntpdate from cron -- DON'T DO THAT!

On Sun, 2002-12-22 at 01:47, John Hasler wrote: > Antoine writes: > > I was one of the people using ntpdate in a cron job, although it was not > > because I was lazy, all my servers have ntpd, I only used ntpdate on > > clients. > > Then your clients should have been connecting to the ntp daemons

Re: ntpdate from cron -- DON'T DO THAT!

On Sun, Dec 22, 2002 at 03:17:50AM +0100, Vincent Lefevre wrote: > > Shouldn't happen. Have you filed a bug report? > > I'm not the administrator of the machines at my lab, so I couldn't > report any useful information. Try typing bug at a shell prompt. If it works, you should be able to at lea

Re: ntpdate from cron -- DON'T DO THAT!

On Sat, Dec 21, 2002 at 04:15:35PM -0800, nate wrote: > it can, and does I've been using it for ages. I do not like to run > ntpd on everything[1]. The less daemons listening on ports the better for me. > ntpd is more accurate then ntpdate, but doing a ntpdate ; > hwclock --systohc works fine for m

Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

On Sat, Dec 21, 2002 at 10:12:56PM -0600, John Hasler wrote: > Michael D. Schleif writes: > > granted, wherever feasible, ntpd is technically the best . . . > > Do you know of some benchmarks comparing ntp and chrony? I thought chronyd did not implement all of the time protocol RFC and had fewer

Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

Michael D. Schleif writes: > granted, wherever feasible, ntpd is technically the best . . . Do you know of some benchmarks comparing ntp and chrony? -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

"N. Thomas" wrote: > > * Kirk Strauser <[EMAIL PROTECTED]> [2002-12-21 19:56:20 -0600]: > > > Contrary to what you may have heard, ntpdate does not keep your system > > > clock synced. > > > > In fact, you can *force* ntpdate to slew the clock rate to achieve > > accuracy rather than stepping it;

Re: This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

* Kirk Strauser <[EMAIL PROTECTED]> [2002-12-21 19:56:20 -0600]: > > Contrary to what you may have heard, ntpdate does not keep your system > > clock synced. > > In fact, you can *force* ntpdate to slew the clock rate to achieve > accuracy rather than stepping it; see the '-B' option. Yes, but t

Re: ntpdate from cron -- DON'T DO THAT!

Vincent writes: > Does [chrony] set the hardware clock? It can, using the 'trimrtc' directive (this is not properly documented: a bug). -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe".

Re: ntpdate from cron -- DON'T DO THAT!

On Sat, Dec 21, 2002 at 19:50:39 -0600, John Hasler wrote: > Vincent writes: > > This is what is used on the machines at my lab, but the daemon sometimes > > dies. > > Shouldn't happen. Have you filed a bug report? I'm not the administrator of the machines at my lab, so I couldn't report any use

This is incorrect advice (Re: ntpdate from cron -- DON'T DO THAT!)

On Sat, 2002-12-21 at 17:51, N. Thomas wrote: > Contrary to what you may have heard, ntpdate does not keep your system > clock synced. Also ignore the foolish recommendations to run ntpdate > from a cron job. > > ntpdate works like date(1), but it sets your clock's time to that of an > ntp server

Re: ntpdate from cron -- DON'T DO THAT!

Vincent writes: > This is what is used on the machines at my lab, but the daemon sometimes > dies. Shouldn't happen. Have you filed a bug report? > So, I wouldn't say that this is a good solution, unless there is a way to > restart ntpd automatically (by cron?) when it dies. man inittab Or tr

Re: ntpdate from cron -- DON'T DO THAT!

Lance Simmons writes: > Won't that still be bad for the machines on the internal network? Their > clocks will regularly be reset. If he runs it frequently and the clocks in the clients aren't too bad the changes will be less than a second and therefor unlikely to damage anything. He'd be better

Re: ntpdate from cron -- DON'T DO THAT!

* Lance Simmons <[EMAIL PROTECTED]> [2002-12-21 19:16:56 -0600]: > On Sat, Dec 21, 2002 at 07:28:20PM -0500, N. Thomas wrote: > > > > Why don't you just run ntpd on the one machine that talks to the > > higher stratum servers and use ntpdate for your internal network? > > Won't that still be bad

Re: ntpdate from cron -- DON'T DO THAT!

On Sat, Dec 21, 2002 at 18:51:24 -0500, N. Thomas wrote: > If you want to keep your clock in sync use ntpd -- that's what it was > designed for. This is what is used on the machines at my lab, but the daemon sometimes dies. So, I wouldn't say that this is a good solution, unless there is a way to

Re: ntpdate from cron -- DON'T DO THAT!

Nate writes: > As above, only 1 system sync's to an external server, and it is a .gov > server, time.nist.gov or something. I was about to write that you should not use a stratum 1 server, but this page implies that NIST doesn't mind at all.

  1   2   >