<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Keeping your System clock current, automatically via Network Time Protocol (NTP)</title>
	<atom:link href="http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html</link>
	<description>Ubuntu Linux Tutorials,Howtos,Tips &#38; News &#124; Oneiric,Natty,Maverick</description>
	<lastBuildDate>Mon, 06 Feb 2012 15:40:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Shane Bishop</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-9344</link>
		<dc:creator>Shane Bishop</dc:creator>
		<pubDate>Sun, 24 May 2009 04:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-9344</guid>
		<description>Just because I&#039;ve noticed hits on the url above (which no longer works), here&#039;s the proper one:
http://ntp.shanebishop.net/eluna/
The &#039;server&#039; is now processing over 200 clients, and still uses virtually no resources on a P3 1.0 Ghz with 368MB RAM.</description>
		<content:encoded><![CDATA[<p>Just because I&#8217;ve noticed hits on the url above (which no longer works), here&#8217;s the proper one:<br />
<a href="http://ntp.shanebishop.net/eluna/" rel="nofollow">http://ntp.shanebishop.net/eluna/</a><br />
The &#8216;server&#8217; is now processing over 200 clients, and still uses virtually no resources on a P3 1.0 Ghz with 368MB RAM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Bishop</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-503</link>
		<dc:creator>Shane Bishop</dc:creator>
		<pubDate>Sun, 09 Nov 2008 14:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-503</guid>
		<description>ntp is still the best solution. It takes into account other factors to keep your clock time stable all the time, whereas ntpdate is accurate only at the time you run it. Most of the time, that doesn&#039;t matter, but if you have a system that gets heavily loaded, or has some other odd factors, your time can really get messed up by the time you run ntpdate again. Besides, ntp uses no resources, and is still easier to setup, even if the gui doesn&#039;t work on 8.04:
apt-get install ntp
That&#039;s it, it&#039;s already configured, it gets started automatically when you install it, and it will always be running.
If you want proof on the resources, check out http://jabber.shanebishop.net/eluna/ ... The memory graph doesn&#039;t really tell you much, but it&#039;s currently using 300k of RAM, and serving from 30-100 ntp clients at any given time.</description>
		<content:encoded><![CDATA[<p>ntp is still the best solution. It takes into account other factors to keep your clock time stable all the time, whereas ntpdate is accurate only at the time you run it. Most of the time, that doesn&#8217;t matter, but if you have a system that gets heavily loaded, or has some other odd factors, your time can really get messed up by the time you run ntpdate again. Besides, ntp uses no resources, and is still easier to setup, even if the gui doesn&#8217;t work on 8.04:<br />
apt-get install ntp<br />
That&#8217;s it, it&#8217;s already configured, it gets started automatically when you install it, and it will always be running.<br />
If you want proof on the resources, check out <a href="http://jabber.shanebishop.net/eluna/" rel="nofollow">http://jabber.shanebishop.net/eluna/</a> &#8230; The memory graph doesn&#8217;t really tell you much, but it&#8217;s currently using 300k of RAM, and serving from 30-100 ntp clients at any given time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-502</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Fri, 23 May 2008 10:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-502</guid>
		<description>COMMENT: On Ubuntu 8.04 the graphical configuration of ntp does not work! Also, ntp is a bit of overkill for what most users need, since it runs continuously in the background, keeping the clock in sync with millisecond accuracy. Hence, remove ntp, in favour of ntpdate, and set things up following the comment of &quot;January 8th, 2007 at 2:50 am&quot; above.

NOTE: Ubuntu 8.04 seems to have problems with cron, so things may still not work as expected.</description>
		<content:encoded><![CDATA[<p>COMMENT: On Ubuntu 8.04 the graphical configuration of ntp does not work! Also, ntp is a bit of overkill for what most users need, since it runs continuously in the background, keeping the clock in sync with millisecond accuracy. Hence, remove ntp, in favour of ntpdate, and set things up following the comment of &#8220;January 8th, 2007 at 2:50 am&#8221; above.</p>
<p>NOTE: Ubuntu 8.04 seems to have problems with cron, so things may still not work as expected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jj</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-501</link>
		<dc:creator>jj</dc:creator>
		<pubDate>Thu, 13 Mar 2008 01:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-501</guid>
		<description>You can do the above graphically by:
#1 Selecting System&gt;Administration&gt;Time&amp;Date OR Rt clicking the Time &amp; Date in the Upper Rt corner of the screen OR at the CLI enter &quot;time-admin&quot;
#2 enter your password
#3 In the resulting configuration drop-down box select &quot;Keep Synchronized w/Internet Servers&quot; in lieu of  &quot;Manual&quot;
#4 Press the install button to install the alternate /etc/ntp.conf download package.
#5 Confirm your NTP server by double-clicking the &quot;Select Server&quot; button. On Feisty the Ubuntu server is set by default and should be enough for the desktop.</description>
		<content:encoded><![CDATA[<p>You can do the above graphically by:<br />
#1 Selecting System&gt;Administration&gt;Time&amp;Date OR Rt clicking the Time &amp; Date in the Upper Rt corner of the screen OR at the CLI enter &#8220;time-admin&#8221;<br />
#2 enter your password<br />
#3 In the resulting configuration drop-down box select &#8220;Keep Synchronized w/Internet Servers&#8221; in lieu of  &#8220;Manual&#8221;<br />
#4 Press the install button to install the alternate /etc/ntp.conf download package.<br />
#5 Confirm your NTP server by double-clicking the &#8220;Select Server&#8221; button. On Feisty the Ubuntu server is set by default and should be enough for the desktop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Name</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-500</link>
		<dc:creator>Name</dc:creator>
		<pubDate>Mon, 08 Jan 2007 02:50:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-500</guid>
		<description>&quot;Setting and maintaining the time
 The ntpdate utility can be used to set time to the current time using a clock server. The one I use is clock.psu.edu as follows:
# ntpdate -u clock.psu.edu

 Theoretically, you should be able to run the ntpd daemon to connect to a server and keep your machine clock correctly synchronized at all times. However, I&#039;ve never been quite successful in finding a server willing to support this.
Using cron to maintain correct time
 The cron daemon runs services hourly, daily, weekly and monthly. These services are executable script files maintained in these directories:
/etc/cron.hourly
/etc/cron.daily
/etc/cron.weekly
/etc/cron.monthly

 Here is the file I use: /etc/cron.weekly/setclock.cron
#!/bin/bash

clock=clock.psu.edu

/usr/sbin/ntpdate -u $clock &gt;&amp; /dev/null

 The reason for the &gt;&amp; /dev/null redirection is that you want to make sure that cron scripts send nothing to standard output or standard error. If you want to use this script, make sure it is executable:
# chmod +x /etc/cron.weekly/setclock.cron&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;Setting and maintaining the time<br />
 The ntpdate utility can be used to set time to the current time using a clock server. The one I use is clock.psu.edu as follows:<br />
# ntpdate -u clock.psu.edu</p>
<p> Theoretically, you should be able to run the ntpd daemon to connect to a server and keep your machine clock correctly synchronized at all times. However, I&#8217;ve never been quite successful in finding a server willing to support this.<br />
Using cron to maintain correct time<br />
 The cron daemon runs services hourly, daily, weekly and monthly. These services are executable script files maintained in these directories:<br />
/etc/cron.hourly<br />
/etc/cron.daily<br />
/etc/cron.weekly<br />
/etc/cron.monthly</p>
<p> Here is the file I use: /etc/cron.weekly/setclock.cron<br />
#!/bin/bash</p>
<p>clock=clock.psu.edu</p>
<p>/usr/sbin/ntpdate -u $clock &gt;&amp; /dev/null</p>
<p> The reason for the &gt;&amp; /dev/null redirection is that you want to make sure that cron scripts send nothing to standard output or standard error. If you want to use this script, make sure it is executable:<br />
# chmod +x /etc/cron.weekly/setclock.cron&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Name</title>
		<link>http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html/comment-page-1#comment-499</link>
		<dc:creator>Name</dc:creator>
		<pubDate>Mon, 08 Jan 2007 02:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/keeping-your-system-clock-current-automatically-via-network-time-protocol-ntp.html#comment-499</guid>
		<description>Isn&#039;t this a better way of doing it:

http://www.cs.wcupa.edu/~rkline/Linux/odds-ends.html</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t this a better way of doing it:</p>
<p><a href="http://www.cs.wcupa.edu/~rkline/Linux/odds-ends.html" rel="nofollow">http://www.cs.wcupa.edu/~rkline/Linux/odds-ends.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

