The other approach I had considered was to test for how much the timer had drifted at safe periods, then pause and resume the service to get back on synch. It doesn't elimate the problem, but allows me to specify where it skips ahead to the next minute. This would eliminate the risk of my missing a significant time period.
In reply to Re: Re: Time Drift when using Win32::Daemon::Simple
by rah
in thread Time Drift when using Win32::Daemon::Simple
by rah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |