I'm trying to figure out a bug report that I received the other day with hwclock, and I'm curious if anyone else has seen the behavior. I'm not able to reproduce reliably as the user is: https://bugs.archlinux.org/task/31416 The bits about fsck can be ignored, they're merely a symptom. I was able to trace this behavior with an educated guess back to 839be2ba6. I suppose part of the issue is that I'm fairly oblivious about how the hwclock works, and the interaction with the timezone, particularly when the clock is set to UTC. The reporter is using sysvinit with Arch Linux's initscripts. hwclock's involvement in his case boils down to the following call on bootup: hwclock --systz --utc --noadjfile Of course, the --systz flag in there won't work as it used to anymore, but the commit message I've picked out doesn't seem to match the behavior it changes. Any insight would be appreciated. Cheers, Dave -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
