Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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 the following problem,After a power failure my machines time is off by 2 hours.I am not using UTC so according to me it should not adjust time according to daylight savings,etc.What could cause this,I am sure the time is correct before the power failure.Thanks for any help...
I'm using FC3 kernel 2.6.12-1.1381_FC3 on that machine.I am updating time through ntpdate at 2:30 am through a cron job,but if the power fails before that the time will be wrong until then.It only happens on the one machine,the other machines time is still correct after power failure.My timezone is southfrica/Johannesburg so why will it change after the power failure?
Its a remote machine,so I'll check the battery later,but i'm pretty sure that's not the problem,because the machine is still pretty new,so thae battery should be fine.but thanks for your help.
It seems so yes,is there anything else that would cause the time to be set back by 2 hours?except a faulty battery.As i said i'm not using UTC,but still it seems to reset to it.very weird...
There's no /etc/timezone but there's a /etc/sysconfig/clock where you can change the timezone ,mine="Africa/Johannesburg", which is right,the UTC,mine is set to false,and ARC ,which i'm not to sure what it does but mine is false.
I am not updating time to any ntp server other than the ntpdate i run through a cron,so that shoul not be the problem as well...
Hallo again.I've "fixed" it by just running a ntpdate command when the system boots up again after a power failure,but in the background the time is still getting set back by two hours for some reason,i'm just setting it right again every time,so if someone knows what it might be please let me know,but i guess its fine as it is now...
Distribution: Debian Etch (w/ dual-boot XP for gaming)
Posts: 282
Rep:
Sounds a bit unlikely, but is the machine dual-boot by any chance? Windows handles daylight-savings differently to Linux, with the result that my Linux(/system) clock was put back (or forward, I forget which) an hour when I booted into Windows. The 'solution' was to disable Windows' "Automatically update the clock for daylight savings" thing, which I still think does it the wrong way. It did mean the time was an hour out in Windows though, which may or may not be appropriate for you (if it's even relevant).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.