From: "Sina Bahram" <sbahram@nc.rr.com>
To: <speakup@braille.uwo.ca>
Subject: RE: Help with date and redhat 9
Date: Sun, 26 Oct 2003 18:13:21 -0500 [thread overview]
Message-ID: <000201c39c16$c0ade020$6401a8c0@quantum> (raw)
In-Reply-To: <Pine.LNX.4.58.0310261613350.3839@homerun.midsouth.rr.com>
Thanks for your response.
The only one of those I have is rdate. I'm going to go see if I can
figure out how to pass a server or multiple servers to it. and then
figure out how to add it to the chron like Alex was talking about.
Take care,
Sina
No trees were destroyed in sending this message. However, a large number
of electrons were terribly inconvenienced.
-----Original Message-----
From: speakup-admin@braille.uwo.ca [mailto:speakup-admin@braille.uwo.ca]
On Behalf Of Adam Myrow
Sent: Sunday, October 26, 2003 5:20 PM
To: speakup@braille.uwo.ca
Subject: Re: Help with date and redhat 9
You don't use date to set the time from a time server. The date command
is only for manually setting the date. There are several ways to set
the time from a remote server. Some commands include netdate, rdate,
and ntpdate. If you have it, ntpdate is the most accurate. You can
pass it multiple servers, and it will pick the best one. If you are
really into time, you could have ntpd running all the time to actually
adjust the speed of the clock within Linux so that it stays within a few
MS of the correct time. For a good list of time servers, go to
http://www.eecis.udel.edu/~mills/ntp/servers.html and find several near
you with open access. Then, assuming you have ntpdate available, you
could try "ntpdate server." For example, "ntpdate time.nist.gov
time-b.nist.gov" would ask ntpdate to get the time from two of the NIST
servers and pick the one it thinks is the most accurate and set your
clock to it. Hope this helps.
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
my mutt shit itself Alex Snow
` Help with date and redhat 9 Sina Bahram
` Chuck Hallenbeck
` Gregory Nowak
` Sina Bahram
` Barry Pollock
` Sina Bahram
` Adam Myrow
` Sina Bahram [this message]
` Sina Bahram
` Chuck Hallenbeck
` Sina Bahram
` Chuck Hallenbeck
` Sina Bahram
` Chuck Hallenbeck
` Sina Bahram
` Alex Snow
` Sina Bahram
` Gregory Nowak
` Sina Bahram
` Alex Snow
` Alex Snow
` Sina Bahram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000201c39c16$c0ade020$6401a8c0@quantum' \
--to=sbahram@nc.rr.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).