Setting time in Slackware
Ted Gervais
I need to set the time on my Slackware system (9.1) and wonder how we do
it.
What I had been doing was using an alias as follows:
alias netdate='netdate 132.163.135.130'
This no longer works. Maybe a new site would be helpful.
Or is there a better way?
Anyone please..
---
Here about the young Chinese woman who just won the lottery?
One fortunate cookie...
Ted Gervais
Coldbrook Nova Scotia
Canada B4R1A7
Jan-Ove Jansson
Jim
> I need to set the time on my Slackware system (9.1) and wonder how we do
> it.
>
> What I had been doing was using an alias as follows:
>
> alias netdate='netdate 132.163.135.130'
>
> This no longer works. Maybe a new site would be helpful.
> Or is there a better way?
>
> Anyone please..
I generally use: ntpdate <insert time site>
where a time site is one of listed on
http://www.eecis.udel.edu/~mills/ntp/servers.html
Thomas Ronayne
Ted Gervais wrote:
> I need to set the time on my Slackware system (9.1) and wonder how we do
> it.
>
If you just want to set it every so ofter, use
/usr/sbin/ntpdate -v 140.221.9.6 198.147.38.140
(Those servers are stratum 2 servers you ought to be able to get to.)
Better, set up NTP if you're connected all the time, say with DSL, T1,
T10, etc.
Ted Gervais
time so maybe I should set up something to run through CRON or something
like that.
But for now - I just needed to know how to get the time set up correctly. I
did it with the help of the other two who responded. I will look further
into NTP maybe to see if this will help.
Thanks again everyone for your help and patience..
"Thomas Ronayne" <tronaRE...@ameritech.net> wrote in message
news:G%FBb.15340$P%1.142...@newssvr28.news.prodigy.com...
William Park
> Thanks everyone for your input on this time issue. I am on line all the
> time so maybe I should set up something to run through CRON or something
> like that.
> But for now - I just needed to know how to get the time set up correctly. I
> did it with the help of the other two who responded. I will look further
> into NTP maybe to see if this will help.
>
> Thanks again everyone for your help and patience..
You should be aware that using NIST (stratum 1) is frowned upon. You
should use stratum 2 or 3.
--
William Park, Open Geometry Consulting, <openge...@yahoo.ca>
Linux solution for data management and processing.
RayzrShrp
Setting up a time server client under slackware looks from the above
post simple enough but is there really any reason for it on a home
computer? I do have a small network and it would be nice to sync all
my boxs with the same time. I'm sure slackware is capable to do this
so would I just direct my windows boxs at my linux box for the time
server and voila??
Thomas Ronayne
> Setting up a time server client under slackware looks from the above
> post simple enough but is there really any reason for it on a home
> computer? I do have a small network and it would be nice to sync all
> my boxs with the same time. I'm sure slackware is capable to do this
> so would I just direct my windows boxs at my linux box for the time
Yes, it is easy -- you set one of them up to the outside world (with
NTP) going to a stratum 2 time server (or group of stratum 2 servers),
and you set the others up to use your outside world connected machine
(which magically became a stratum 3 server).
The line,
/usr/sbin/ntpdate -v server_address
is only to set the time on boot, you should not use it in any kind of a
loop -- that's what ntpd is for.
It takes a little reading in the HOWTO; you need to understand what to
put in your ntp.conf file for both your outside world machine (so it
will serve time to your other machines) and the ntp.conf file(s) on your
inside world machines.
William Park
> Yes, it is easy -- you set one of them up to the outside world (with
> NTP) going to a stratum 2 time server (or group of stratum 2 servers),
> and you set the others up to use your outside world connected machine
> (which magically became a stratum 3 server).
>
> The line,
>
> /usr/sbin/ntpdate -v server_address
>
> is only to set the time on boot, you should not use it in any kind of a
> loop -- that's what ntpd is for.
>
> It takes a little reading in the HOWTO; you need to understand what to
> put in your ntp.conf file for both your outside world machine (so it
> will serve time to your other machines) and the ntp.conf file(s) on your
> inside world machines.
For home situation, it's much easier to set time using 'netdate' or
'ntpdate' on one machine, and have all other machines set from that
machine using 'netdate' (port 37, Time).
Blumf
Hash: SHA1
Larry Alkoff wrote:
> Upon checking my Slackware 9.1 there is no longer any instance
> of ntpdate or rdate. There is ntpd but I understand this is hard to
> setup and overkill for a home machine.
'ntpdate' has been retired from the ntp suite of programs. 'ntpd -q' can be
used instead.
Blumf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/2FNjMid3IcxolsoRAgAaAJoCSDRzkTO+MoKg/CoFk1EaG4E3WACfdcvZ
jzpdRLzpVPsjFA1CO7EpCR8=
=VPVl
-----END PGP SIGNATURE-----
Jim
> Apparently Slackware 9.1 has changed the way time is to be set.
>
> Upon checking my Slackware 9.1 there is no longer any instance
> of ntpdate or rdate. There is ntpd but I understand this is hard to
> setup and overkill for a home machine.
>
> It _appears_ that Slack 9.1 is designed to use netdate or, in more
> complex environments like servers, ntpd.
>
> Would some Slack 9.1 users confirm that this is the case?
>
> Is there any way to set the hardware clock like the systohc option in
> rdate?
In my Slack 9.1 install:
-rwxr-xr-x 1 root bin 34100 Sep 11 23:47 /usr/sbin/ntpdate*
Thomas Ronayne
William Park wrote:
>
> For home situation, it's much easier to set time using 'netdate' or
> 'ntpdate' on one machine, and have all other machines set from that
> machine using 'netdate' (port 37, Time).
Easier, yes, but where's the learning experience? 'Sides, NPT is not
rocket science to set up.
Eef Hartman
> Is there any way to set the hardware clock like the systohc option in
> rdate?
SW 9.1 already reads at bootup (in rc.S) cq sets at shutdown (in rc.6)
the hardware clock. It uses (and has been using for some time) the
/sbin/hwclock program for that. See also the man page for hwclock.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M....@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
Bartosz Oudekerk
Hash: SHA1
Larry Alkoff <nob...@nowhere.com> is thought to have typed
the following text on 2003-12-13:
> up? Does cron care if a script hangs up? It's not clear if run-parts
> (written by Patrick?) simply _starts_ each script in a directory and
> goes on to the next or does it wait until each script finishes.
>
What's not clear about it? It's a basic shell-script, nothing fancy.
less $(which run-parts), shows me it runs each script in the
foreground from a for-loop, so yes, it will only go on to the next when
the current one has finished.
> I'm trying to think of a way to stop the script that runs netdate
> after a few minutes but haven't come up with a starting point yet.
>
Couldn't you try something like this?
#v+
#!/bin/bash
netdate -v $SERVERS &
sleep $TIMEOUT
killall netdate
#v-
- --
Bartosz Oudekerk
Play Rogue, visit exotic locations, meet strange creatures
and kill them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/2w1s256ZyNYAOpkRAhTgAKCfE+IemdBvhR1AR1LOuFRq8tUquwCeLq+H
fljaop0tojO9GcxVIcVyKcA=
=u3g3
-----END PGP SIGNATURE-----
William Park
> I've noticed that a number of contributors to this thread have
> recommended using netdate.
>
> This is of course not really a Slackware question,
> but when I use netdate it frequently hangs up.
>
> The command
> netdate -v 129.6.15.28 132.163.4.102 131.107.1.10 207.200.81.113
You are using Stratum 1 servers, ie.
time-a.nist.gov
time-B.timefreq.bldrdoc.gov
time-nw.nist.gov
nist1.aol-ca.truetime.com
You know you shouldn't do that. Use Stratum 2 or lower.
/dev/rob0
Larry Alkoff wrote:
> I finally found a long list of stratum 2 servers on google. Most are
> unresponsive.
Probably because, as was mentioned eariler in this thread, netdate is a
different, older, and now less widely-used protocol (37/tcp) than NTP
(123/udp). You probably found David Mills' list of NTP stratum 2 NTP
servers; that page is hosted at the University of Delaware,
Some public ntpd servers still serve time, but many do not. There is no
reason I know to use netdate over ntpdate (ntpd -q).
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply
William Park
> On 13 Dec 2003 21:33:46 GMT, William Park <openge...@yahoo.ca>
> wrote:
>
>
> >> netdate -v 129.6.15.28 132.163.4.102 131.107.1.10 207.200.81.113
> >
> >You are using Stratum 1 servers, ie.
> > time-a.nist.gov
> > time-B.timefreq.bldrdoc.gov
> > time-nw.nist.gov
> > nist1.aol-ca.truetime.com
> >You know you shouldn't do that. Use Stratum 2 or lower.
>
> marked as such.
>
> I finally found a long list of stratum 2 servers on google. Most are
> unresponsive.
>
>
> Larry
There are lots. See
http://www.eecis.udel.edu/~mills/ntp/servers.html
http://www.ntp.org
Also, you may want to consider
time.apple.com
time.windows.com
which are stratum 2 (ntp only) servers. They are not listed, but Apple
and Microsoft do have more money than any Linux company (other than
Novell, maybe).
R.
>>
>>You are using Stratum 1 servers, ie.
>> time-a.nist.gov
>> time-B.timefreq.bldrdoc.gov
>> time-nw.nist.gov
>> nist1.aol-ca.truetime.com
>>You know you shouldn't do that. Use Stratum 2 or lower.
>
> marked as such.
>
> I finally found a long list of stratum 2 servers on google. Most are
> unresponsive.
>
> Will keep trying.
>
> Larry
Go ahead and keep using the servers you are using.
Here are the servers you can use. Right from the nist.gov list. Read the
page, they say nothing about not using them. I would think if they
didn't want you to use them, they would say so. Don't you think!
http://www.boulder.nist.gov/timefreq/service/time-servers.html
All of the IP numbers you listed are on this list. Go ahead and keep
using them.
/dev/rob0
posting for the record anyway.
In article <iiiqtv8ockhti2och...@4ax.com>,
Larry Alkoff wrote:
> I found a site that listed stratum 2 time servers. Most of them don't
> work. Of 76 servers, only 16 worked! Some connected but refused to
What was this site? Google for "stratum 2 time servers" with the "I'm
feeling lucky" button brings up this page:
http://www.eecis.udel.edu/~mills/ntp/clock2a.html
But, there are 171 listed, and 78 in the USA alone.
These are, however, NTP servers. They are not "Time" servers. It is not
surprising that a few NTP sites still offer Time protocol service; nor
is it odd to find that most do not.
I Googled a bit and I cannot find any comparable list of Time protocol
servers. NIST seems to have a few, but not even close to 76 sites. Some
old mirrors of the above udel.edu page list fewer than the present
number, but ... a list of NTP servers is not applicable to a non-NTP
client! It's quite like trying to tune in 88.9 MHz FM on a radio set to
the AM band. You MAY find a station at the corresponding spot on the AM
dial, but it most assuredly is not 88.9 MHz FM.
(Oops, do analog radio dials still exist?)
> In my small home network I really don't need the time to be
> superaccurate <g>.
True, but neither is it needed to be inaccurate. NTP (ntpdate) provides
better performance in addition to better accuracy. Again I know of no
single advantage in using Time protocol over NTP. Anyone who does know
of one is invited to post a correction.
OH OH OH ... I think I may have thought of a reason why one might not
use ntpdate ... it is in a separate, optional package. OTOH netdate is
in the required "tcpip" meta-package. And netdate at 11KB is about 1/3
the size of ntpdate: such shameful bloat!! ;)
Keith Keller
Hash: SHA1
On 2003-12-15, /dev/rob0 <ro...@gmx.co.uk> wrote:
> (Oops, do analog radio dials still exist?)
My 1985 Camry has analog radio dials. My old Pioneer
receiver has a volume dial. :)
- --keith
- --
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/3h3MhVcNCxZ5ID8RAvMcAJ9xhJ4seR5KFKr32xN6qXj/ZjGJoACfXgg4
X9kEB9OcakEzgWi2I9c1XW8=
=kum7
-----END PGP SIGNATURE-----
AthlonRob
Hash: SHA1
On Mon, 15 Dec 2003 11:43:21 -0800, /dev/rob0 <ro...@gmx.co.uk> wrote:
> (Oops, do analog radio dials still exist?)
Unfortunately, they do. My clock radio, which I purchased about three
months ago, uses an analog dial, making it more complicated to find the
right station than a digital one. Why they even put numbers on the
faceplates of these things, I simply do not understand.
--
Rob | If not safe,
Email and Jabber: | one can never be free.
athlonrob at axpr dot net |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/3h8ahm6KEoOOAe0RAmQuAJ40VZ5eTMej5JQ7mOTWisE69Ja22gCdHecc
vTbFAC4Lv4IxUAlWLHTM5cU=
=OZzY
-----END PGP SIGNATURE-----
William Park
> (Oops, do analog radio dials still exist?)
Well, I still have and use old clock-radio. :-)
> True, but neither is it needed to be inaccurate. NTP (ntpdate)
> provides better performance in addition to better accuracy. Again I
> know of no single advantage in using Time protocol over NTP. Anyone
> who does know of one is invited to post a correction.
>
> OH OH OH ... I think I may have thought of a reason why one might not
> use ntpdate ... it is in a separate, optional package. OTOH netdate is
> in the required "tcpip" meta-package. And netdate at 11KB is about 1/3
> the size of ntpdate: such shameful bloat!! ;)
Also, Time/Daytime is served by 'inetd' itself.
Getting back on issue, though... I think using Stratum 1 servers, say,
once a day or two should be okey. Here are Stratum 2 NTP servers that
also run Time or Daytime:
time.nrc.ca -- NTP (2), Time
time.chu.nrc.ca -- NTP (2), Time
clock.fmt.he.net -- NTP (claims 1, but is 2), Time, Daytime
Bartosz Oudekerk
Hash: SHA1
/dev/rob0 <ro...@gmx.co.uk> is thought to have typed the
following text on 2003-12-15:
> (Oops, do analog radio dials still exist?)
>
My Sansui has one.
But it isn't really a recent model, although it does sound better than
more recent models.[0][1]
[0] As long as there's a strong signal.
[1] more recent models by other manufacturers that is, I only recently
found out Sansui was back in business, but haven't had the chance
to hear any of their kit.
- --
Bartosz Oudekerk
Play Rogue, visit exotic locations, meet strange creatures
and kill them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/3i2m256ZyNYAOpkRAoBaAKCfY8LZfAFRswI62Rpu2zC6mtXLFwCfXZnC
sRcfR5T0ihH7TD/s/g8y2JI=
=nQD1
-----END PGP SIGNATURE-----
Joost Kremers
> [1] more recent models by other manufacturers that is, I only recently
> found out Sansui was back in business, but haven't had the chance
> to hear any of their kit.
my father bought a sansui when he was in his early twenties. that system
lasted for about 20 years. he bought another sansui set then, but it didn't
have the same quality. it certainly didn't last as long...
--
Joost Kremers joostk...@yahoo.com
Slackware doesn't have any quirks. Other distros have quirks. Slackware's
just pure Linux.
Bartosz Oudekerk
Hash: SHA1
Joost Kremers <joostk...@yahoo.com> is thought to have
typed the following text on 2003-12-15:
> Bartosz Oudekerk wrote:
>
> my father bought a sansui when he was in his early twenties. that system
> lasted for about 20 years. he bought another sansui set then, but it didn't
> have the same quality. it certainly didn't last as long...
>
I seem to get that with a lot of "modern" equipment, while technology
is supposed to get better, things break sooner. This is especially true
of harddrives IME, the bigger they get the shorter they last.
On Sansui: It is being imported by the same company that imports Akai
equipment (which also used to be very good, long ago), so chances are
they simply bought the name when Sansui filed for bankrucy, and started
to use it only now.
- --
Bartosz Oudekerk
Play Rogue, visit exotic locations, meet strange creatures
and kill them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/3jct256ZyNYAOpkRAuOkAJ0XNXn1bJNczXwjJd1WzzpJKnkbdACdFSsn
p7av/Ct7Wd3Uag5PnoEpP7I=
=YA2a
-----END PGP SIGNATURE-----
ASD...@asfdad.org
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
pgp trash troll delete
> On Sansui: It is being imported by the same company that imports
> Akai equipment (which also used to be very good, long ago), so
> chances are they simply bought the name when Sansui filed for
> bankrucy, and started to use it only now.
What on earth does this have to do with slackware?
Please refrain from using pgp unless it is necessary. Show some
respect for the other posters.
How many times do you have to be told?
cordially, as always,
rm
skippy steve
>
> How many times do you have to be told?
>
All of them.
Mike Denhoff
Bartosz Oudekerk <bartosz@see_my_GnuPG-key.com> wrote:
> I seem to get that with a lot of "modern" equipment, while technology
> is supposed to get better, things break sooner. This is especially
> true of harddrives IME, the bigger they get the shorter they last.
>
It is not so much because they are bigger, but because they are being
made more cheaply.
I have been to a couple of talks given by scientists working for hard
drive manufacturers. Some years ago they were designing hard drives to
last for 5 years. But recently, they have relaxed that requirement to 2
or 3 years. What is the reason? Consumers want lower prices.
It's sad that people tend to be so short sighted.
Mike
David Bolton
been posted, excuse me for not noticing.)
On 15 Dec 2003 21:14:31 GMT, William Park <openge...@yahoo.ca> wrote:
>Getting back on issue, though... I think using Stratum 1 servers, say,
>once a day or two should be okey. Here are Stratum 2 NTP servers that
First, their opinion on using Stratum 1 servers:
"Rules of Engagement
As the load on the hosts supporting NTP primary (stratum 1) time service
is heavy and always increasing, clients should avoid using the primary
servers whenever possible."
So it sounds like, "Hands off those Stratum 1's!" Besides, they list
something like 174 Stratum 2 Servers. Plenty to go 'round.
Second, you can get a list of Stratum 2 from their site, however they
don't like people linking to the list, so I'll refrain from posting it
here. This is what they said:
"Note that the lists are updated frequently, so please do not cache them
and please do not reveal links to the lists themselves. Note that the
names of the lists are changed on a regular basis in order to discourage
direct links."
So, instead, just go to their site and find the link 'public NTP server
list.', which brings up a choice between the Stratum 1 or 2 Server list.
HTH,
David