Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a similar problem on a dual boot. It seems that everything is fine as long as I run only one system. But if I switch between the systems (I just booted accidentally into Linux because Windows update wanted to reboot and Linux is my default system) the clock runs about 40 min late. In Windows, the automatic adjustment is switched off. On Linux however, xntpd is running. Could that be the problem?
'it seem everything is fine as long as you run one OS'
--yup, that's the point. as soon as DST rolls around and it's time to update your clock, your OS will recognize that and change your clock. so if you're running happily along in linux, DST comes and goes, and you then need to boot to windows for some reason, when you do, you'll get your clock mucked.
'about 40 mins late'.. eh, you got me on that one... i'm sure xntp is playing a role, though
I guess I found the solution (at least for my system): SuSE recommends to set the system clock to 'local time' instead of 'GMT' on dual boot systems, claiming that Windows uses the same setting. I now tried to use GMT instead and see, the clock runs correctly.
About those 40 min I am not that sure anymore Maybe the clock wasn't set correctly... sorry!
yes, windows defaults to sys clock of localtime... when running dual boot, you need to think about both/all OSes when considering the clock, and i like to recommend that the OS you use most on any multi-boot box be the ONLY one set to roll the clock for DST
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.