[tkined] bug with job command?

Chad Smith (csmith@bbg.adc.com)
Wed, 1 Dec 1999 12:02:00 -0600 (CST)

Hi all,

I'm using scotty2.1.10 and have a small problem (easy workaround) with
updating a clock on my application. I use the job create command to
create a timer that updates the clock every minute. The problem is when
I set the system time backwards. The -time configuration option of the
job is incremented by the number of seconds (it appears) as I set the
system time back. This causes my clock to not be updated for potentially
long periods of time, depending on how far back I set the time.

For example, if I set the system time back 1 hour, the -time option is
incremented by 360000, which means it will take an hour before the clock
gets updated again.

My solution is to kill the job and restart it whenever the system time is
changed, but that won't work if an admin changes it on the command line
(the GUI provides an interface for setting the time). So my question is,
is this a bug with scotty or is it a known "that's what it's supposed to
do" problem? If it's a bug, any simple way I can fix it in the release
that I'm using?

Thanks very much,
-chad

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.