Just can't stay away
Joined: 2009/4/28 4:57 Last Login
: Today 7:43
From Adelaide, Australia
Group:
Registered Users
|
Open a shell window and type:
time save
The time gets saved to the system clock (and not the battery clock, which setclock is for) but it resets it to the start of the current minute.
I.E If it is 23:43:37 and you type "time save", it'll set to the clock to 23:43:00.
This bug is also in the "Date" command. Date 23:00:35 will ignore the "SS" of HH:MM:SS even though it says it's valid in the documentation.
There is also another issue i'm having, where I am losing time, without even rebooting. I'll come back after a few hours and have lost 30 seconds or so, without any reason.
Sometimes I reset the computer, and it's set to yesterday, or some other strange date and time. I can never get the clock to be stable, i'm constantly updating it.
Edit: I initially thought it might not be a bug, since you cannot set the seconds in the Time preferences utility, however you can click the "save" button in the time utility and it won't reset it back to the start of the current minute, so I think it is a bug when using it on the command line.
To think of it, what is the point of the "save" option on the command line in the "time" command? You can set the time using "c:date", and using the save parameter in "time" is only useful for... well, nothing?
The setclock documentation refers to "setclock load" being in the Startup-Sequence. I don't ever remember that being in the Startup-Sequence, whether it be OS3.1, 3.5, 3.9 or 4.1.
As I said before, the time loses seconds or minutes without me rebooting or doing anything in particular. So, adding it to the startup-sequence wouldn't help in this case.
Edited by MickJT on 2010/9/12 15:49:52 Edited by MickJT on 2010/9/12 15:54:45 Edited by MickJT on 2010/9/12 15:57:51
|