🚀 go-pugleaf

In csu.general John Erickson <jerickso@holly.colostate.edu> wrote:
: In csu.general Xylen <mctupper@holly.colostate.edu> wrote:
:> But do I have to set it every single time my screensaver activates? In
:> gnome I can reset the clock, although gnome complains about it. I was
:> doing that for awhile, but it gets aggravating to have to set the clock
:> everytime my screensaver kicks in. I'm hoping for something that will
:> automatically update the clock, say every hour, to the correct time
:> without my having to do it manually. I don't know what that command is,
:> but I suppose I could put it in cron.hourly if I had to.

: Short answer.. no, you shouldn't have to set the clock hourly.  But you
: knew that.

Yeah, setting the clock is one thing...  its the whole 
getting-the-clock-to-stop-stopping thing that hurts.  I have an
idea, though:  Is is possible that you are using some of the APM
stuff?  When APM goes into effect, the harware (CMOS) clock still
runs, but the linux software clock, of course, can't run.  This 
sounds like the problem.  To test it, try this:

clock -r   # Read the CMOS clock and print it.
date       # Read the software clock and print it.

If I am close, then the CMOS clock should always be correct, and
the software one is slipping.

The problem is that I don't know where to fix this problem...

If nothing else, you might be able to call clock -s  every time 
a screen saver quits.

You sure do get the interesting problems... :)

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michael J. Dwyer                    Digital Watches are a neat idea!
mdwyer@holly.ColoState.edu       http://WWW.CS.ColoState.EDU/~dwyer/
Computer Science Major                      Amateur Radio Tech N0ZAP