When I shut down the machine everything is as it should be. Time set from the net, hwclock synced. When I boot again, time is set several hours into the future. This is an additive process, when I don't set the correct time it drifts with every boot even days into the future (until boot is denied, because files are too far in the future). I tried to get rid of that behaviour by doing:
sntp -P no -r pool.ntp.org
I renamed /etc/adjtime which looked like this:
22292.201093 1289670517 0.000000
Now it looks as follows:
0.000000 1289733620 0.000000
To no avail. What could cause that and how can I correct it?
My computer has two physical hard drives. Up till now, the first hard drive was for Windows XP and Windows 7, the second was used for file storage. I just installed Lucid Lynx on the second drive. The two problems are as follows.
<s>1. When I boot into Windows 7, the clock is set ahead by five hours, even as the time zone remains the same. </s> Terribly sorry. Found the answer in another thread. Should have searched.
2. I have kept the Windows 7 boot loader (choice of 7 or XP) on the first hard drive, and put Ubuntu and grub on the second hard drive. That way, if I want to load Ubuntu, I press F9 for the hp boot menu and select the second hard drive. From there, I would like this to boot straight into Ubuntu. How do I keep the grub boot menu from appearing? Should I just edit grub.cfg, so it has a timeout value of 0?
I have Fedora in dual boot with windows on a laptop. I have a weird clock problem. If I get the clock set correctly in Fedora, then it's 4 hours too fast in Windows. When I fix it in Windows and then restart into Fedora, it's 4 hours too slow in Fedora!Why are they competing with each other and how do I get them to both be correct?
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.
I am running a LAMP system with CentOS 5.4.The clock just automatically shifted backwards by 19 hours and 30 minutes crippling some of my reports and probably damaging something else along the way.The router supplying IP to this server is a DD-WRT and shows proper time.By the way what does that mean? time drifted by that 33.667 ms?
But I did it and still don't show me the option to change the clock to 12 hour format, I tried changing the es_NI language (Spanish Nicaragua) and gives me the option of 12 hours, but the languages of programs like firefox, thunderbird, openoffice change to English.What can i do to have language es_ES and 12 hours format on my clock? or es_NI language with firefox, thunderbird etc. in spanish?
I've been frustrated with several problems I've been experiencing with Karmic Koala. The one I'll mention in this post is the fact that it randomly decides to adjust the system clock ahead 6 hours. I believe this began happening when I set the location for the system time that displays in the top panel. I'm guessing that the 6 hours is the fact that I'm in the US Central Time zone.
i probably messed up the clock somehow... I think during install. Linux keeps messing up windows clock... And vice versa... When the clock in windows is correct (say, 2 PM), the clock in Linux when i reboot says 4 PM... And when i set up the clock in Linux to the correct time (in this case 2 PM) and boot into windows, windows clock says 12 PM...
Of course, when i correct it in windows, linux clock gets messed up again... 2 hours early or forward, idk... I'm not sure what i did to make this happen... Maybe has something to do with hardware clock... I don't wanna constantly correct time whenever i change systems...
I decided to install Ubuntu on my desktop after the setup went well on my laptop and I liked the OS. I already had Windows 7 and Backtrack 9 installed on my HDD, so when I was in setup I took the 200gb partition for BT9 and formatted SDA5 to ext3 with "/" as the root. Then checked "format" and selected SDA5 from dropdown list and continued to install.Everything went smooth in the installation and I was prompted to reboot which I did assuming I would soon see a GRUB screen. Instead I got an error saying
and then the computer just freezes. I've tried to boot from CD but I just get "CD-ROM Boot Priority ...Boot Ready" and then after about 30 seconds it tries to boot from the HDD and I get the same error.I've read that I need to configure GRUB somehow but I have no idea how to do that and I can't boot anything from a CD because it just waits and then jumps to the HDD. I guess what i'm asking is if there is a way to configure GRUB from the BIOS menu or make it possible to be able to boot from a CD.
I've kind of ignored this until I had the major parts of my ubuntu said up. During videos I cannot click on the little bars to move ahead in the video this happens sometimes in ..... and in other stuff. Also if an add that like stretches onto the screen comes up I might not be able to click exit. In both cases my mouse thing turns into the little hand for clicking but it doesn't work.
I noticed that every, say, 5 times I boot CentOS 5.4, a find search is initiated that takes several hours. For example: find . -name rd=rmdir -print I'm not sure if it's related, but, I do have a "alias rd=rmdir" in my .aliases. Would changing it to "alias rd=/bin/rmdir" avoid this problem? I'm using zsh. Is this search necessary?
I'm using a very simple conky script to diplay the date and time on my desktop. I've noticed that he conky clock is a few seconds early compared to the time displayed in the right hand side of the top panel (Natty). I guess both displays are based on the same "internal" time, so I'm left wondering how this could happen, and how to sync back the clocks.
It seems that Conky is in sync with the system date, while the panel clock is 2 seconds late (on my system). Checked with while true; do date; sleep 0.1; done
I had cloned a centos 5.6 installation from virtualbox virtual machine to physical box. Everything work fine. However, the time showing in os using date command differs from bios time by roughly 4 hours. I am running ntp services which sync the time with another centos server on the network. It appears that some services are using virtual clock and some use physical clock. How do I get rid of virtual clock and only use physical clock?
I'm trying to sync my clock. I think I would like to do this by the "ntpd" daemon running. I think it should start up on boot, but it doesn't.
I have the following in my /var/log/syslog: Jul 18 23:44:14 neo ntpd: ntpd firstname.lastname@example.org Sun Oct 17 13:45:13 UTC 2010 (1) Jul 18 23:44:14 neo ntpd: proto: precision = 0.634 usec Jul 18 23:44:14 neo ntpd: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Jul 18 23:44:14 neo ntpdate: step time server 220.127.116.11 offset -0.505108 sec
Other posts say if ntpd and ntpdate run too close together, they cause one to think the other is locking a resource. It works to type "ntpdate pool.ntp.org" to manually update the clock. My Debian version is squeeze (6.0.2)
It works to start the ntpd daemon manually: ... sudo /etc/init.d/ntp start ... Starting NTP server: ntpd.
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 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?
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?
I am hosting two Virtual Servers both running Centos 5.3 on a host machine also running the same OS. The VM software in use is Xen, as supplied with the OS.The host machine's time and date is fine, however both Virtual Servers are running ahead of real time consitantly.Running /etc/init.d/ntpd restart will resolve the issue however one of these is running MailScanner and when the time suddenly goes backwards, sometimes by as much as an hour, it stops working properly.
I am currently running Ubuntu 10.10 x32 on an Acer AMD Athlon x2 64. I can be using the computer, or it can be idle, when I hear the fan kick on (very loud) and the system monitors show the CPU at 100%. The problem started after an update in 10.04; updated to 10.10 and the problem has continued.
I am using Intel Fortran compiler and experience a weird behavior
i have a subroutine writing data to netcdf called from the main program and causing a library error. when debugging i saw that the program first jumps to line 411 of the source code and only then to the first executable line of the code at 96 (the source is attached). when looking at the assembler code i see the same thing.
the netcdf error sais the unlimited dimension is defined more then once and that is waht is done in line 411 compiler flags were: -g -C -traceback -check all -debug all -w95 -save -cpp -w90 -w95 -w -vec-report1 -r8 -i4 -heap-arrays
For about a month now, my mouse has been jumping to one of the corners of my screen every few minutes (normally the top-left). I also had a problem where the right mouse button would double-click 90% of the time.
I just replaced my mouse a few minutes ago, and now the right button works fine, but the cursor keeps jumping to the corner of the screen.
I'm fairly certain this is not a hardware problem, since switching mice did not fix the problem.
after finally being able to find the right configuration file for the Synaptics driver (I still think the change from HAL to udev was too silent...), I have gained the ability to configure my TouchPad. One Issue has been bothering me for a long time now: When moving the cursor from left to the right, at a certain position the mouse cursor jumps to the right edge of the screen.Here is the output of synclient while moving the finger constantly from left to right to illustrate the issue:
Note that the value of RightEdge was changed by me in order to see if it has something to do with the issue. It has not, the cursor jumps at the same position, regardless of this value.
I'm after fresh install of Fedora x64, did all updates. I have wireless pci card TP-LINK TL-wn510G (Atheros chipset) which was detected correctly.
Everything is working smoothly until I start to download from internet in firefox (or in konqueror - no difference). On increased network activity my mouse cursor starts to lag/jump when moving - it's almost impossible to do anything using mouse when there is file download. On minor traffic, like browsing webpages, I don't notice such behaviour. I checked if its rather because of hdd activity not the network, but no - when copying big file on hdd everything works fine. I'm also experiencing huge ssh lag/jitter despite the ping is low. I fired top when downloading, but there is no process eating cpu in suspicious way. I have a regular usb mouse. On the same computer I have installed Win 7 and OpenSuse and nothing like this happens on that systems.
I think there might be a some kind of conflict between wifi card and usb mouse (they share resources) but don't know how to check/repair. Could you please tell me how should I proceed to check what is going on. I haven't modified any hw settings, the installation went w/o any errors.