🚀 go-pugleaf

In csu.general Xylen <mctupper@holly.colostate.edu> wrote:
> I have poked around the faqs, and man pages, but I can't find any
> mention of the screensaver affecting the clock or how to update the
> clock when it needs it. Does anyone here have a clue? (about fixing the
> clock)

ewww...  FVWM.

Anyhow..  the date command should work for you.  As root:
date MMDDhhmmCCYY.ss
MMDDhhmm is the minimal date format to set the clock.

-- 
John Erickson | john@vistasolutions.net
              | jerickso@evilsoft.org

John Erickson wrote:
> 
> In csu.general Xylen <mctupper@holly.colostate.edu> wrote:
> > I have poked around the faqs, and man pages, but I can't find any
> > mention of the screensaver affecting the clock or how to update the
> > clock when it needs it. Does anyone here have a clue? (about fixing the
> > clock)
> 
> ewww...  FVWM.
> 
> Anyhow..  the date command should work for you.  As root:
> date MMDDhhmmCCYY.ss
> MMDDhhmm is the minimal date format to set the clock.

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.

Xylen
-- 
  __^__                                   __^__ 
 ( ___ )---------------------------------( ___ ) 
  | / | Irony: Bill Gates claims to be    | \ | 
  | / | making a stable Operating System, | \ | 
  | / | and Linus Torvalds claims to be   | \ | 
  |___| taking over the world.            |___|
 (_____)---------------------------------(_____)

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.

Longer answer.. If you're on a real net connection (unlike me), you could
always use one of the atomic clock time clients to set it for you.

Alternative to fixing it.. You could always not use it..  :)  dpms will 
allow you to blank your screen or power it down if you'd like.
xset dpms standbyTime suspendTime offTime
spec'd in seconds of course...

Question.. Is it screwing with the software clock or the BIOS clock?
I know there is a semi-trivial way to check the BIOS clock (w/o rebooting
atleast) but I can't remember right now.  MDwyer knows it though.  What
screensaver stuff are you running?  X-Screensaver is what I remember you
saying.  All that I know is I've never had a problem with XScreensaver.

-- 
John Erickson | john@vistasolutions.net
              | jerickso@evilsoft.org

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

Okay, so I'm pulling an Adam and replying to my own post, but who am I
to go against tradition. Yes it was an APM problem. Once I shut off the
APM, and let the screensaver do what it wanted, the clocks stayed in
synch. All I wanted was for my screen to turn off after 30 minutes of
running the screensaver. I thought I needed the APM to do that. Silly
me, Linux knows better, and lets me turn the screen off without using
the APM. So now my questions is--What is the APM good for?

Xylen,
I'm still up at this hour because my program STILL doesn't work right
and it was due 2 hours ago. :(

Michael Dwyer wrote:
> 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.

Right after rebooting I get this:

# clock -r
Thu Apr 13 23:48:28 2000 -0.117809 sec
# date
Thu Apr 13 23:48:31 MDT 2000

Now I let the screensaver take over, and about 12 minutes later I get:

#clock -r
Fri Apr 14 00:13:31 2000 -0.711014
# date
Thu Apr 13 18:13:35 MDT 2000

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

Well not only is the SW clock slipping, it is going back in time! So it
appears that it may be the APM. Is it possible to turn that off?


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

Well, rebooting works, but that is rather drastic.

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

Well that is better than rebooting.

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

Gee thanks. It's pretty bad when I can get a reputation for interesting
problems when I don't want them in the first place.  :)

Xylen

In csu.general Xylen <mctupper@holly.colostate.edu> wrote:
: running the screensaver. I thought I needed the APM to do that. Silly
: me, Linux knows better, and lets me turn the screen off without using
: the APM. So now my questions is--What is the APM good for?

I don't really know about that.  If nothing else, it should handle that
clock strangeness for you.  It kind of a bad sign that instead of handling
the clock, it munged it up...  Jerickso has it working on a Laptop, though,
I think -- he prolly has more of an idea of APM's worth.  For the most
part, Linux machines are usually servers that are always on, so APM is
kind of stupid...

FWIW, you can handle X screen turning off with xset dpmi.  Just make
sure you remember that the time setting is in SECONDS, and not minutes.
Took me a while to figure out why my screen would turn off in 45 seconds...

And, you can spin your hard drives down with hdparm -S

: I'm still up at this hour because my program STILL doesn't work right
: and it was due 2 hours ago. :(

. . . don't wanna talk about it . . .

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