I'm running windows 7 and the F12 Beta (although the same issue existed in my f11 distro) on an asus g71 bb. When ever I boot into windows my time is correct. If I boot into to F12 my time is wrong. Usually by 4 hours. If I change it in Linux when I boot into windows I end up switching the time on my windows partition. I tried searching the forum (rather casual I'll admit) and couldn't find any solutions.
I've been running arch linux, with my clock set to UTC with no problem. Recently I installed slackware on a different partition. During the setup I chose to set my clock to 'local time' instead of UTC by accident. Now in slackware my clock shows the wrong time. Also in arch it shows the same wrong time.
I booted back into slackware and ran pkgtool to enter the setup again, and changed my time to UTC. But this makes no difference. My clock is still wrong in both slackware and arch. Do I need to reboot after changing my clock settings in slackware before it takes effect? how the clock or the setup works.
I noticed today that my F13 date was one month out i.e October 30th instead of September 30th.Time was okay. I tried to adjust it manually but no success. Now if I try to start up I get to the first blue screeen but then it says something like "last mountpoint date was October 30th = now September 30th which is in the future" (not exact wording). Time zone is correct and not set to network time or UTC. I'm dual booting with WinXP and date and time is correct and Time Zone is correct. System time is correct. So now to get into F13 I have to manually set the system time to 30th October.Which is OK for the 1st reboot but reverts back to the correct date on the next reboot. WinXP boots ok.
I have a strange problem with my Ubuntu Natty virtual machine running under VirtualBox on OSX.One day last week, my clock on the top bar in Gnome stopped displaying the correct time (I'm not running Unity). I'm on GMT, so right now it should be 9:31, but it's showing 3:31, so I think it's something to do with TimeZones. If I go into the date and time applet, the time is initially wrong but after a second sets itself to the correct GMT Time. The timezone is correclty set as London and it makes no difference if I unlock and set it again or select manual or automatic from internet time.
From a bash prompt, the "date" command shows: "Tue Sep 20 03:33:35 CDT 2011".If I run "sudo dpkg-reconfigure tzdata" I am correctly set as London. Upon exiting the commnand I'm shown the correct London time, but then typing "date" again shows the CDT time again.The clock is correct in OSX. This has been working fine for a month or two - I think it stopped working after an update last week. Any ideas?
I've set-up dual boot on my laptop. Ubuntu installed first, then Windows 7 so it uses Grub2 to control the booting on start-up. I've noticed that my system clock goes out by an hour on both OS's, I change the clock to correct time & on reboot the time is usually (not always straight away) an hour behind. Has anyone else had this problem & know how to fix it?
When installing I perhaps mistakingly told Fedora it should use the BIOS clock and now it shows the wrong time, 1 hour ahead of my time-zone GMT+0. If I try and go to the preferences and set the time the 'Advanced Options' one of which I need are grayed out, I need the 'Use local time source' option to be unchecked. Could somebody tell me a workaround or the command-line commands to tell it not to do this anymore?
Try as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
I restored my .kde directory after changing some stuff unrelated to my clock and now all plasma clocks are exactly 5 hours faster than my system time (the correct time).I've set the time zone for Date&Time in System Settings properly and that's working well and I've ALSO gone into the time zone settings for the plasma widgets and switched between UTC and Local manually but that doesn't do anything.
I recently noticed that the time displayed in the Gnome Clock applet is exactly (or nearly so) one second behind NTP time.I have a NTP server on my small network to which I sync my other PCs. Some of the applications I run are critical of time and need sub second accuracy - I am also a bit of Time Nut as well.My NTP server is OK. My PCs can sync to my NTP server OK. My applications which require precise time get the right time from NTP - BUT - the time displayed in the GNOME Clock applet is always behind one second!I have spent much time searching for others with similar problems and their solutions but so far nothing - hence my asking here, why do I see this behaviour and what can I do about it
When I travel, I would like to tell my laptop that I, as a user, am in a different time zone that what the OS may think is local. And I would like the clock on my desktop (default Gnome bar date/time display) to show the local time.
Instead, I currently have to use sudo and change the system time... (click on the clock, choose time settings, set system time -- there are no other choices given). The applet thing allows me to add other locations, but they only show up if I click on the icon, as extra times below the main one.
I have been using clock() for calculating CPU time and time() for calculating Wall time. However, since time() does not provided milli / microsecond accurancy, I started using gettimeofday() as below to calculate wall time,
Certain times, I have been noticing that WALLTIME calculated is lesser than CPUTIME. I am not sure why ? Double checked the simple code, nothing seems to be wrong in simple subtraction. My understanding was always WALLTIME (elapsed time) remains higher than CPUTIME (compute time). I run my application on head node of a Linux cluster comprising of 24 compute nodes, each with 8 processors.
Trying to adjust my clock settings!I am running KDE 4.4.3 on Squeeze, on an 64bit laptop.(I used the AMD64 net install version)How can I fix the time settings so it shows 5:00pm instead of 17:00:00So far I have not been able to find a cure
I have dual boot on my comp. Windows XP and Fedora 11 Now in both systems time zone is set to Belgrade ( which is my time zone), but when I setup clock in fedora to be, let's say 16.15h, then when I swich to windows it says time is 14.15h. When I setup in windows on 16.15h, and I swich to fedora, it says time is 18.15h. So I can't get accurate time on both systems in no way.
By default, Fedora 11 sets my clock to military time. For example it says 16:22. I would like it to show civilian time (or at least know how to do it) I logged into the clock settings and had to put in the root password, but couldn't find where you do this. If you scroll on the time for hours, it just goes from 0 to 23 and back, not to AM and PM like some others.
I done searches for "clock" and found similar threads, but no real fix that is working for me. My clock resets when I boot into linux. It does not happen in windows or bios even on cold boots. The battery is replaced and good** the old battery was by all measures dead (0.6v), but still seemed to have enough power for the clock, since windows tested fine with it.
I have tryed setting it to local time, UTC.. etc... My timezone is GMT (london). "sudo /sbin/hwclock --systohc" Although I have windows, I do not use it except the few times to test this, so no conflict.
When I boot into Debian (lenny) my clock is always 4 hours slow. Whether I set it manually, or set it to get it's time from the network, the next time I boot into debian, it's back to being 4 hours slow.
I have Ubuntu 10.04.1 32bit installed on my flash drive so wherever I go I can have my own mini personal computer, but one problem I'm having is every computer it is run on the next time it's rebooted to the OS on the hard drive it has UTC time instead of the actual time for the timezone you're in that Windows uses. So is their a way I can make Ubuntu not automatically change the clock to what it wants?
I have cron jobs running and the timing is critical, because I'm running Nessus scans on production servers. If I hit them at the wrong time, I'm toast. But when I check the cron log, I see that it is an hour off. Here is the output for the command "clock": Wed 31 Mar 2010 03:01:26 PM CDT -0.257677 seconds
And this is the tail of the cron log: Mar 31 16:00:01 nes-001 CROND: (root) CMD (/Nessus/Targets/NessusScriptDataCenterScan.test) Mar 31 16:01:02 nes-001 CROND: (root) CMD (run-parts /etc/cron.hourly) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly): starting 0anacron Mar 31 16:01:02 nes-001 anacron: Anacron started on 2010-03-31 Mar 31 16:01:02 nes-001 anacron: Normal exit (0 jobs run) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly): finished 0anacron
Cron thinks it is 4:00 p.m., but it's really 3:00 p.m. How do I tell Cron what time it is? (Stopping and restarting the crond service did not change it.)
I'd like to have two gnome clock applets, one with the regular default time and date in the upper right hand corner (the default) and another set to epoch time. However, I can't figure out how to set the second gnome clock applet to display the epoch time. I'm running FC12.
I have this problem for a while but didn't notice it until lately(i did reboot the machine for few months). Now that i reboot it frequently i notice that the clock is always not what is supposed to be. I'm in Toronto, Canada so it should be GMT -5:00. Sometimes it shows GMT-6, sometimes -10, now is GMT -11. Anyone would know why i have this issue? I'm running Suse11.1 on a 64 bit. My laptop which runs on 32 bit is working fine.(well probably different versions for kernel and kde.(whatever was in th repository to be updated i updated)
18.104.22.168-0.2-default Version 4.3.4 (KDE 4.3.4) "release 2"
Dual boot system. Boot Linux Fedora 13 and the hardware clock is set to GMT. Boot Windows 7, time is wrong, as it expects the hardware clock to be set to the local time. reset the hardware clock each time I reboot in to the other O/S.
I'm having a problem with the time on one of my servers jumping forward into the future. We run serveral CentOS 5.4 servers running Xen, some up to date and some a little older. The one in question is running 2.6.18-164.el5xen, with xen-libs-3.0.3-94.el5_4.2 and xen-3.0.3-94.el5_4.2. On this server are several Xen virtual machines, also running CentOS 5.4 with kernel 2.6.18-164.el5xen. One in particular has problems with the clock keeping proper time.
We use NTP (ntpd) to sync time to a central server in the company. Our NTP set-up works fine, and we have problems on only a couple of servers out of many. The problem I see is that one one particular Xen virtual machine, the clock will suddenly jump forward into the future, usually by several minutes but once by more than an hour. This has obvious implications for software running on the machine. Software such as Oracle grid control agent will restart itself under the (incorrect) assumption that it has been hung for several minutes with no activity. Oracle database will cope gracefully, but applications that refer to the clock will be confused.
We detect these time jumps because we have Nagios checking the clock on each host against the centralised time server (Nagios's check_ntp plugin). Nagios will suddenly report a clock offset that is miles into the future. Following the time jump, ntpd on the host in question will re-sync the time. Ntpd keeps the time steady, ticking just a few milliseconds per second until real time catches up with the server. i.e. Nagios will report the time as being 10 minutes ahead, then a minute later the host will be 9 minutes ahead, and then a further minute later the host will be 8 minutes ahead of real time. The clock on the host stays running very slow until it eventually is correct.
My server is a VPS which is running with CentOS. I found a wield problem that the system clock always runs faster than the hardware clock. For example, I set system clock and hardware clock both on 20:00. After about half an hour, the system clock will be 20:34/5 which is wrong while the hardware clock remains correct (20:30).
I just installed antix. It asked for time zones and I set all of that up but it is 3hrs off. My computer clock is correct, why can't I just set up antix to recognize my computer clock? Or why doesn't it just use that as a default?
I'm setting the hardware clock on RHEL 5.1 system using /sbin/hwclock --systohc. After setting the clock I issue a date command followed by a /sbin/hwclock --show from within a script to get fast resolution and I see that the hardware clock precedes the system time on average by .5 seconds. I would think the clock should be identical after setting.
I am running GNOME on a slackware 10.1 sys. I want my desktop clock to sync itself with some remote time server...like in MS windows. If I cant do that, how do I manually reset the sys time so the desktop app will read the correct time?
Now that I'm able to connect to Internet via my MC760 wireless modem on /dev/ttyUSB0, I am losing time! I have lost 5 minutes while online for 1/2 hr. Yes ntpd is running. What is strange is that right now, I'm in town at coffee shop and using wireless. I'm not losing time at all. This isn't the first time I've noticed the loss of time. It's been happening every since I was able to connect with the usb modem. I just had to come to town and use wireless to see if the problem existed while on wireless (b43). While being connected via the MC760, I've also noticed that the cpu temp rises and the fan runs quite a bit more than when not connected via the MC760. Here is the top portion of output of "top" code...
I had to boot into my Windows 7 install on my laptop for the first time in a few months and I noticed that the Windows clock was 4 hours ahead. Windows sync'd its time with the internet, then I booted back into Debian (Lenny) and my clock was now 4 hours behind. Both OS's are set to the same time zone (EDT). The minutes were correct in both systems. Could the fact that EDT is UTC-0400 be relevant?