Corinna Vinschen writes:
> There's an internal counter which is initialized by the first Cygwin
> process started in a session. So time chanegs made by a Cygwin process
> are seen by other Cygwin processes in the same session, but time changes
> outside of Cygwin or outside of the same session are not seen, unless all
> Cygwin processes in a session are stopped and restarted. This will be
> fixed at one point.
So running something like this
date -s `cmd /c echo %time%`
either _ad lib_ or as a cron job every few days will limit the damage,
at the cost of losing a bit across the board each time you do it,
since the situation is _not_ symmetrical. That is, because date -s in
Cygwin _does_ reset the windows clock. . .
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 651-1426, e-mail: h...@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
