Ubuntu Time Management This page gives useful information about the way that Ubuntu manages time by changing the timezone, setting up synchronization using Network Time Protocol NTP , and adjusting servers. Click on the System menu on the top panel, go into the Administration sub-menu, and click on Time and Date. Click on the currently selected time zone to bring up the selection map.
Click in the general area of your location on the time zone map, the map will zoom in. Sat May 8 Universal Time is now: This can be scripted if required. Time Synchronization using NTP This page describes methods for automatically keeping your computer's time accurate.
This is extremely useful for servers, and is also recommended for desktop machines. Basically a client requests the current time from a server, and then uses the servers response to set its own clock. Beyond this simple description, there is a lot of complexity. There are multiple tiers of NTP servers, with the tier one NTP servers connected to atomic clocks often via GPS , and tier two and three servers spreading the load of actually handling requests across the internet.
The client software is a lot more complex than you might think as it has to factor communication delays, and adjust the time in a way that does not affect the other processes that run on the system. Luckily all that complexity is hidden from the user. Click on the System menu on the top panel, go into the Administration sub-menu, and click on Date and Time.
Select the configuration option Keep synchronized with Internet servers You may get a dialog box informing you that NTP support has to be installed. You are now finished and you can click Close or you can customize the NTP servers default is ntp.
Command Line ntpd ntpdate is a bit of a blunt instrument as it can only adjust the time once a day in one big correction. The ntp daemon ntpd is far more subtle as it calculates the drift of your system clock and continuously adjusts it in small increments.
Using ntpd there are no large corrections that could lead to inconsistent logs for instance. The cost is a little processing power and memory, but for a modern system this is negligible. To setup ntpd in versions of Ubuntu 7. This is OK, but you might want to use several servers to increase accuracy and resilience, and you may want to use time servers that are geographically closer to you. You may have to enter your password to continue. Select Configure Servers Enable the box next to your choice of server s or add your own.
However, a system's clock is likely to drift considerably between reboots if the time between reboots is long. In that case it makes sense to correct the time occasionally. The easiest way to do this is to get cron to run it every day. This is a really good idea which uses round-robin DNS to return an NTP server from a pool, spreading the load between several different servers.
Even better, they have pools for different regions - I am in New Zealand, so I use nz. You can also Google for NTP servers in your region, and add these to your configuration. Multiple Boot Systems Time Conflicts Operating systems store and retrieve the time in the hardware clock located on your motherboard so that it can keep track of the time even when the system does not have power.
This causes problems in a dual boot system if both systems view the hardware clock differently. Windows Registry Editor Version 5. Windows Time service will still write local time to the RTC regardless of the registry setting above on shutdown, so it is handy to disable Windows Time service with this command if time sync is still required while in Windows use any third-party time sync solution: The ntpdate and ntp-doc packages may also be useful. Which configuration file is it using?
Your client must be configured to use the supplied NTP servers. NTP most commonly 'fails' if it cannot resolve the servers in its configuration file at startup this can happen if DNS isn't available during boot. Also, if NTP is unable to keep the local clock reasonably accurate it gives up and terminates see below.
I have various systems on unreliable networks so I use a simple script to bounce NTP if needed: Failing that, try ntp. Can these servers be resolved? Can these servers be reached? What's NTP up to? You can leave it off, but don't be surprised if the resolved names don't match names in the ntp. The smaller the better! The smaller the better. NTP attempts to fix your local clock to keep accurate time. If your local clock drifts too fast usually HW problems or IRQ lockups or somesuch then NTP either keeps resetting your clock or gives up and terminates.
Fix the drift problem and NTP will behave. UbuntuTime last edited