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?

Larry

--
Larry Alkoff N2LA - Austin TX
My address is: larryalk is_at mindspring dot com

-----BEGIN PGP SIGNED MESSAGE-----
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-----

On Thu, 11 Dec 2003 10:31:18 +0000, Larry Alkoff wrote:

> 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*

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.

Larry Alkoff <nobody@nowhere.com> wrote:
> 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.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

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
usually fails on the first site and then hangs up attempting to
contact the second site. The hang up seems to be unrelated to the
failure at the first site.

Perhaps the second site is down tonight but apparently there is no
timeout so the whole command hangs. Will a script in cron.daily hang
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.

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.

Larry Alkoff

--
Larry Alkoff N2LA - Austin TX
My address is: larryalk is_at mindspring dot com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Larry Alkoff <nobody@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+IemdBvhR1AR1LOuFRq8tUquw CeLq+H
fljaop0tojO9GcxVIcVyKcA=
=u3g3
-----END PGP SIGNATURE-----

On 13 Dec 2003 12:59:48 GMT, Bartosz Oudekerk
<bartosz@see_my_GnuPG-key.com> wrote:


>> 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-


I let my setdate script, which calls netdate, run while hung up
since early this am. Killall netdate run in another terminal killed
netdate and the script very nicely.

I'll put your idea in the script to prevent a hangup over say 5
minutes.

Thanks very much for your help.

Larry Alkoff

--
Larry Alkoff N2LA - Austin TX
My address is: larryalk is_at mindspring dot com

Larry Alkoff <nobody@nowhere.com> wrote:
> 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.

--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>
Linux solution for data management and processing.

On 13 Dec 2003 21:33:46 GMT, William Park <opengeometry@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.


Actually I didn't know these were stratum 1 servers. They are not
marked as such.

I finally found a long list of stratum 2 servers on google. Most are
unresponsive.

Will keep trying.

Larry

--
Larry Alkoff N2LA - Austin TX
My address is: larryalk is_at mindspring dot com