Re: new time functions

[Guido Flohr <gufl0000@stud.uni-sb.de>]

Hi!

On Wed, Jun 03, 1998 at 09:24:37PM +0200, Julian Reschke-FJR010 wrote:
> Hmmm,
> 
> I think I already understood all of this, however, it didn't seem
> to produce the expected results. I will have to retry.

Please let me know.  I forgot:  There was a nasty bug in the
time setting stuff that produced the result that you described:
After a reboot the time made a leap of two hours forward on
my system.  I thought this was fixed now (see synch_timers in
time.c) but maybe the bug still exists.

The bug didn't occur on my machine anymore but who knows ...

> 
> In the meantime: I think the documentation for the return value
> for the Ssystem clock mode call is wrong. Could you please
> check that?

Yes, there is an error in the doc.  Konrad, could you fix that:

=== Cut ===

--- ssystem.doc~        Fri May  1 07:08:42 1998
+++ ssystem.doc Fri Jun  5 16:55:30 1998
@@ -219,7 +219,7 @@
  100   CLOCK_UTC       cmode   NULL    0

 GET_CLOCK_MODE called with an ARG1 of -1 inquires the kernel's notion
-of the hardware system clock.  If the command returns non-zero the
+of the hardware system clock.  If the command returns zero the
 hardware clock is considered to tick in UTC,  if it returns a positive
 non-zero value it is considered to tick in local time.  Every other
 positive value sets the current clock mode.  For 0 it is reset to UTC,

=== Cut ===

Ciao

Guido
-- 
http://stud.uni-sb.de/~gufl0000
mailto:gufl0000@stud.uni-sb.de