Tried to set my time using kde and the kcmshell clock crashes before
opening. I'm now on slack-9.1 (kde-3.1.4). When I made the last change
I was using slack-9 (probably kde-3.1.2 at that time). Anyone else
having this problem?

I couldn't find any other way to change the clock back an hour, so had
to use reboot and do it in the BIOS. Is there a utility (other than the
buggy kcmshell) on slack to change the clock back?

mark

mark wrote:
> I couldn't find any other way to change the clock back an hour, so had
> to use reboot and do it in the BIOS. Is there a utility (other than the
> buggy kcmshell) on slack to change the clock back?

'man date' and 'man hwclock'

do yourself a favour and ditch KDE. it keeps you from learning. ;-)

--
Joost Kremers
since when is vi an editor? a discussion on vi belongs in
comp.tools.unusable or something... ;-)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

On Sun, 26 Oct 2003 18:34:31 GMT, mark <m.a.r.k@earthlink.net> wrote:

> Is there a utility (other than the buggy kcmshell) on slack to
> change the clock back? mark

This is the script I use, which I found on the net:

# cat /sbin/setdate

#!/bin/sh
#lets see what the current system date is
echo The current System date and time is
date
echo the CMOS/Hardware clock date/time is
clock -r
#or if clock is not available
#hwclock --show

#now to set the system date to the most reliable time server
netdate 129.6.15.28 132.163.4.102 131.107.1.10 207.200.81.113
#has the system time changed much?
echo The Sytem and CMOS/Hardware clock date/time will be set to:
date
#now to set the CMOS/hardware clock
clock -w
#or if clock not available try
#hwclock --systohc

#for finding other IPs to use for netdate see the below
# see http://www.bldrdoc.gov/timefreq/serv...e-servers.html

Bryan


--
Give a man a fish, he owes you one fish.
Teach a man to fish, and you give up your monopoly on fisheries.
- Proprietary Software 101
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/nBbjZHkU/XQom+8RAhMbAJ9f78yhaiicJnr45U/qonTric8G7ACdH6G2
dtW8fioqV4/ruRZuTM+5aOo=
=Qoe2
-----END PGP SIGNATURE-----

ntpdate clock.via.net
hwclock --systohc

On Sun, 26 Oct 2003, mark wrote:

> Tried to set my time using kde and the kcmshell clock crashes before
> opening. I'm now on slack-9.1 (kde-3.1.4). When I made the last change
> I was using slack-9 (probably kde-3.1.2 at that time). Anyone else
> having this problem?
>
> I couldn't find any other way to change the clock back an hour, so had
> to use reboot and do it in the BIOS. Is there a utility (other than the
> buggy kcmshell) on slack to change the clock back?
>
> mark
>
>

__________________________________________________ __________
Jingmin (Jimmy) Zhou Mail : jimmy AT mtc.dhs.org
Web : www.mtc.dhs.org ICQ : 19587415

The future is not set. There is no fate but what we make
for ourselves. - Terminator II, Judgement Day
__________________________________________________ __________

On Sun, 26 Oct 2003 18:34:31 GMT, mark <m.a.r.k@earthlink.net> wrote:
>
>
> Tried to set my time using kde and the kcmshell clock crashes before
> opening. I'm now on slack-9.1 (kde-3.1.4). When I made the last change
> I was using slack-9 (probably kde-3.1.2 at that time). Anyone else
> having this problem?
>
> I couldn't find any other way to change the clock back an hour, so had
> to use reboot and do it in the BIOS. Is there a utility (other than the
> buggy kcmshell) on slack to change the clock back?
>
> mark
>

Here's what I did:

(as root)

#date --set='-1 hours'

then

#hwclock --systohc #to sychronize the hardware clock with the system clock.

Now re-boot. Or perhaps kill -HUP 1 will do the job (running init again).

--
Alan C
Post validation at http://tinyurl.com/rv0y

In article <XsUmb.5655$FI2.4578@newsread1.news.atl.earthlink. net>,
mark wrote:
> I couldn't find any other way to change the clock back an hour, so had
> to use reboot and do it in the BIOS. Is there a utility (other than the
> buggy kcmshell) on slack to change the clock back?

The glibc-zoneinfo package does this all automatically, if your time
zone has been correctly configured in "timeconfig". In fact I only knew
that Daylight Savings time had ended when I looked at my system clock
this morning.

This could be a problem if you dual-boot, I guess.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply

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

/dev/rob0 wrote:

| The glibc-zoneinfo package does this all automatically, if your time
| zone has been correctly configured in "timeconfig". In fact I only knew
| that Daylight Savings time had ended when I looked at my system clock
| this morning.
|
| This could be a problem if you dual-boot, I guess.

Actually, I dual-boot, even though I use Linux 90% of the time, and my
hardware clock was automagically changed. I did a full install, so I
figure that my cron has something to do with this...

Morgan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/nE0vlfnum5gzXsQRAkUAAJ4zN+UDUM48hFOJwCLYcc7ZwpSoSw CdHA29
ZbJMCRUSyAjKLolqSKoN+ZY=
=ORE3
-----END PGP SIGNATURE-----

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

Morgan Landry <morganlandry@linuxmail.org> is thought to
have typed the following text on 2003-10-26:
>
> /dev/rob0 wrote:
>
>| The glibc-zoneinfo package does this all automatically, if your time
>| zone has been correctly configured in "timeconfig". In fact I only knew
>| that Daylight Savings time had ended when I looked at my system clock
>| this morning.
>|
>| This could be a problem if you dual-boot, I guess.
>
> Actually, I dual-boot, even though I use Linux 90% of the time, and my
> hardware clock was automagically changed. I did a full install, so I

What I think /dev/rob0 means is that if you dual-boot, it might be so
that both OS's deceide to adjust the clock, so you'll end up having a
the system clock set two hours back instead of one.

> figure that my cron has something to do with this...
>
Nothing at all, you configured your timezone during the installation
with timeconfig. This creates the /etc/localtime symlink to the
zoneinfo file which contains everything about your timezone, including
daylight-savings-time.

- --
Bartosz Oudekerk

Play Rogue, visit exotic locations, meet strange creatures
and kill them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/nFHw256ZyNYAOpkRAnRnAJ98jC7TulRvAtg78JDm4M2EizyDcQ CeJd1k
CNqd1kYkuQXy5Ezl7mPkFdA=
=YIQJ
-----END PGP SIGNATURE-----

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

Bartosz Oudekerk wrote:

| Nothing at all, you configured your timezone during the installation
| with timeconfig. This creates the /etc/localtime symlink to the
| zoneinfo file which contains everything about your timezone, including
| daylight-savings-time.
|

Sw33t. I love learning something new.

Morgan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/nFJXlfnum5gzXsQRAphuAJ9FLaokQ5C2zqmSfENuGK+3IiO7bA CeJ3D8
/krLGSTWA/P92d5a00Qtg9o=
=Rpyc
-----END PGP SIGNATURE-----

Morgan Landry wrote:
>
> Actually, I dual-boot, even though I use Linux 90% of the time, and my
> hardware clock was automagically changed. I did a full install, so I
> figure that my cron has something to do with this...

/etc/rc.d/rc.6

--------
# Save the system time to the hardware clock using hwclock
elif [ -x /sbin/hwclock ]; then
echo "Saving the system time to the hardware clock."
if [ -e /etc/hardwareclock ]; then
HC=`cat /etc/hardwareclock | while read LINE ; do
if [ "$LINE" = "UTC" -o "$LINE" = "utc" ]; then
echo utc
--------