what time?

what time?

Post by perc » Wed, 09 Jun 1999 04:00:00



hello all,
  Every time , i start my linux box . it's clock is wrong. I use date -s
xx:xx to set up it. but next time , linux box start ... the clock is
wrong....


 
 
 

what time?

Post by John Hovel » Wed, 09 Jun 1999 04:00:00


get a new battery for the computer.

It keeps the clock running.  It's basically a watch battery.
-john


> hello all,
>   Every time , i start my linux box . it's clock is wrong. I use date -s
> xx:xx to set up it. but next time , linux box start ... the clock is
> wrong....




 
 
 

what time?

Post by Ian Cottre » Thu, 10 Jun 1999 04:00:00


: hello all,
:   Every time , i start my linux box . it's clock is wrong. I use date -s
: xx:xx to set up it. but next time , linux box start ... the clock is
: wrong....
:

Use 'clock --systohc' to set your hardware clock to the system time (after
you've set the system time with 'date -s xx:xx').  You might have to
'man hwclock' to get the correct man page, but it's all there.
Good luck.........Ian

--
----------------------------------------------------------------------------


Department of Justice                office: (613) 941-5233
284 Wellington Street
Ottawa, ON, Canada
----------------------------------------------------------------------------

 
 
 

what time?

Post by perc » Fri, 11 Jun 1999 04:00:00


thanks



>: hello all,
>:   Every time , i start my linux box . it's clock is wrong. I use date -s
>: xx:xx to set up it. but next time , linux box start ... the clock is
>: wrong....
>:

>Use 'clock --systohc' to set your hardware clock to the system time (after
>you've set the system time with 'date -s xx:xx').  You might have to
>'man hwclock' to get the correct man page, but it's all there.
>Good luck.........Ian

>--
>---------------------------------------------------------------------------
-


>Department of Justice                office: (613) 941-5233
>284 Wellington Street
>Ottawa, ON, Canada
>---------------------------------------------------------------------------

-
 
 
 

what time?

Post by Yuki Ta » Fri, 11 Jun 1999 04:00:00




>Use 'clock --systohc' to set your hardware clock to the system time (after
>you've set the system time with 'date -s xx:xx').  You might have to
>'man hwclock' to get the correct man page, but it's all there.
>Good luck.........Ian

Hi Ian,

I noticed that just a few of my timestamps were 9 hours ahead of me, and since
I'm in Japan, 9 hours ahead of me is a time that doesn't yet exist anywhere in
the world.  In fact, unless someone moves the dateline, it can never be 9 hours
ahead of me, anywhere, ever.  ;-)  (Nine hours *behind* me is GMT.)

Anyway, I pulled out the man page on advice from some folks, and used that
command above -- just as you have suggested for this other fellow.  My system
clock is JST, by the way.  But after doing that, I still get this on boot:

Jun 10 13:38:19 localhost kernel: Freeing unused kernel memory: 60k freed
Jun 10 13:38:19 localhost kernel: Adding Swap: 104384k swap-space (priority -1)

Jun 10 13:38:20 localhost crond: crond startup succeeded
Jun 10 13:38:20 localhost rc: Starting pcmcia succeeded
Jun 10 22:37:54 localhost rc.sysinit: Loading default keymap succeeded
Jun 10 22:37:55 localhost rc.sysinit: Setting default font succeeded
Jun 10 22:37:55 localhost rc.sysinit: Activating swap partitions succeeded
Jun 10 22:37:55 localhost rc.sysinit: Setting hostname localhost.localdomain
succeeded
Jun 10 22:37:55 localhost fsck: /dev/sdc5: clean, 74612/385560 files,
1076737/1542208 blocks
Jun 10 22:37:55 localhost rc.sysinit: Checking root filesystem succeeded
Jun 10 22:37:55 localhost rc.sysinit: Remounting root filesystem in read-write
mode succeeded
Jun 10 22:38:03 localhost rc.sysinit: Finding module dependencies succeeded
Jun 10 22:38:03 localhost fsck: /dev/sdb4 has reached maximal mount count,
check forced.
Jun 10 22:38:11 localhost fsck: /dev/sdb4: 909/221184 files (1.4%
non-contiguous), 142845/883575 blocks
Jun 10 22:38:12 localhost fsck: /dev/sda5: clean, 31/4016 files, 7433/16033
blocks
Jun 10 22:38:12 localhost rc.sysinit: Checking filesystems succeeded
Jun 10 22:38:12 localhost rc.sysinit: Mounting local filesystems succeeded
Jun 10 22:38:12 localhost rc.sysinit: Turning on user and group quotas for
local filesystems succeeded
Jun 10 13:38:15 localhost date: Thu Jun 10 13:38:15 JST 1999
Jun 10 13:38:15 localhost rc.sysinit: Setting clock : Thu Jun 10 13:38:15 JST
1999 succeeded
Jun 10 13:38:15 localhost rc.sysinit: Enabling swap space succeeded
Jun 10 13:38:15 localhost init: Entering runlevel: 3
Jun 10 13:38:17 localhost network: Bringing up interface lo succeeded
Jun 10 13:38:17 localhost network: Bringing up interface ppp0 succeeded

As you see, there are about 13 lines out of the many which are wrong.
The actual boot time was 1:38 pm JST.  At that time, there is no Jun 10 at
22:38 anywhere in this world.  Where it's 22:38, it's Jun 8, not Jun 10.  So,
what do you make of this, and how would you suggest attacking it?

One thing I notice is that the system clock gets set (see above) *after* these
invalid time stamps.  But I sure don't know how to fix this.

Yuki ^_^

 
 
 

1. convert UT time in local time / local time in UT time

hello,

    I try to make a fonction to convert a local time in UT time. i try to
use
     mktime + gmtime + timezone + daylight.... but the result is not OK.
    Please help me....
    The problem is the same when i try to convert a UT time in Local
Time....

    my imput date format is : 'YYYYMMDDHHMMSS'.

    I'am a beginner on Unix (and in english).....

    Does anyone know about a function or an example (in C) .

    Thanks for any help.

2. Need a slightly advanced guru class redirection/process substitution recipe.

3. time time time how can I tell the time

4. Iptables / tc / QOS

5. Daylight time (label) but standard time (time)

6. Help Routing between 100Mb and 10Mb Nets

7. Daylight Savings time, system time, hardware time....

8. KMail and SSL

9. hda : irq time out {busy} from time to time

10. Is the time in gprof CPU time or elapsed time?

11. Time, NTP, cron wrong time

12. local time to unix time conversion.

13. Linux gateway crashes from time to time