Per Jessen wrote:
Roger Oberholtzer wrote:
On Tue, 2011-07-19 at 10:44 +0200, Per Jessen wrote:
Hmm, I think it's a system thing too - see /etc/localtime There are two possible usage scenarios:
1. The hardware is in UTC time, and there is a timezone specified that specifies how to report the local time from the UTC time.
Right.
2. The hardware is in localtime, and there is a timezone specified that specifies how this differs from UTC time.
No, I don't that is an option. It doesn't matter what UTC time when everything is in local time.
No! The kernel always runs in UTC. Or at least it thinks it does and all applications are designed assuming that it does. The hardware clock should preferably be in UTC but may need to be in localtime if the machine dual boots windows. If the hwclock is in localtime, then configuration needs to say what the hwclock offset is. http://linux.die.net/man/8/hwclock The hardware of the machine exists in some time zone and /etc/localtime records the timezone of the physical machine. Each user can then set their own timezone offset from UTC, if it differs from the machine's. A common newbie error is to have the hwclock in localtime, fail to configure the offset (thus defaulting to zero) and everything appears to work. Then a user explicitly sets their timezone and everything goes crazy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org