I've been looking into the date and time set in an Oxygen system, and comparing to a Mandrake system.
The confusion comes this way: * Hardware clock: set value * Hardware clock (hwclock): value displayed * System clock: set value * System clock: value displayed ...and these interact with: * /etc/localtime * TZ It would also appear that the man page for asctime(2) is wrong, and that the variable timezone is NOT set as it says it is. It would also appear that: * hwclock does not shift the time read according to timezone; it just "stamps" the output with the given timezone * hwclock remembers how the RTC was set - thus, hwclock --show may report UTC, or it may report localtime... I'm also getting lost in functions: gettimeofday() tzset() time() localtime() ...which ONE of these gets the timezone right? Then there's header files: #include <time.h> #include <linux/time.h> #include <sys/time.h> *ALL* of these conflict.... And it even appears that busybox date may be reporting the wrong time... sigh... I wrote my own time display program (tz) just for testing purposes - it calls all of the above functions. I'll try to put it up on in the development area with source code. My hypothesis are: * hwclock works differently than I thought * there may be actual bugs in busybox date * I may be mixing up standard C functions, Linux kernel functions, and old obsolete Linux kernel functions Someone give me an aspirin! -- David Douthitt UNIX Systems Administrator HP-UX, Unixware, Linux [EMAIL PROTECTED] _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
