Am 04.07.2011 12:25, schrieb Klaus Brinkmann: > @Denys: > >> How about this? >> >> -//usage: "\n -u Hardware clock is in UTC" >> -//usage: "\n -l Hardware clock is in local time" >> +//usage: "\n -u Assume hardware clock is kept in UTC" >> +//usage: "\n -l Assume hardware clock is kept in local >> time" > > That should make it clear. Yes. > > > > @Walter: > >> Maybe the author can provide a upstream patch. >> i think it is useful information. > we copy the behavior of the "original" tools better wording may help them also. NTL they should also add the time zone for the output.
re, wh > I'm unsure what you mean by "upstream patch". I hope you refer to the > same output that you provided. So here is mine: > > # hwclock -v > hwclock from util-linux 2.19.1 > # hwclock > Mo 04 Jul 2011 12:00:54 CEST -0.016077 seconds > # hwclock --debug > hwclock from util-linux 2.19.1 > Using /dev interface to clock. > Last drift adjustment done at 1309773476 seconds after 1969 > Last calibration done at 1309773476 seconds after 1969 > Hardware clock is on UTC time > Assuming hardware clock is kept in UTC time. > Waiting for clock tick... > /dev/rtc does not have interrupt functions. Waiting in loop for time > from /dev/rtc to change > ...got clock tick > Time read from Hardware Clock: 2011/07/04 10:01:10 > Hw clock time : 2011/07/04 10:01:10 = 1309773670 seconds since 1969 > Mo 04 Jul 2011 12:01:10 CEST -0.031553 seconds > > Does maybe some locale-variable (LC_TIME) affect the output? In any case > here are my settings: > i guess my are the same > On 04.07.2011 11:38, walter harms wrote: >> I tried also and failed. >> NTL hwclock has this information. Maybe the author can >> provide a upstream patch. i think it is useful information. >> >> re, >> wh >> >> >> # hwclock -v >> hwclock from util-linux-ng 2.14.1 >> # hwclock >> Mon Jul 4 11:33:19 2011 -0.947513 seconds >> # hwclock --debug >> hwclock from util-linux-ng 2.14.1 >> Using /dev interface to clock. >> Last drift adjustment done at 1275739456 seconds after 1969 >> Last calibration done at 1275739456 seconds after 1969 >> Hardware clock is on UTC time >> Assuming hardware clock is kept in UTC time. >> Waiting for clock tick... >> /dev/rtc does not have interrupt functions. Waiting in loop for time from >> /dev/rtc to change >> ...got clock tick >> Time read from Hardware Clock: 2011/07/04 09:34:41 >> Hw clock time : 2011/07/04 09:34:41 = 1309772081 seconds since 1969 >> Mon Jul 4 11:34:41 2011 -0.417931 seconds >> >> > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
