Its because there was no full path, added /usr/sbin/ to the front, and it worked fine.. I'll work on setting up ntpd in my (non-existant) spare time.<br><br>Thanks all !!<br><br clear="all">Tim Champion<br><a href="mailto:timchampion@gmail.com">timchampion@gmail.com</a><br>
<br><br><div class="gmail_quote">On Wed, Apr 27, 2011 at 1:42 PM, Tom Pohl <span dir="ltr"><<a href="mailto:tom@tcpconsulting.com">tom@tcpconsulting.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#FFFFFF"><div><a href="http://ntp.org" target="_blank">ntp.org</a> had dns issues earlier this week. I wonder if they had another outage. Has this worked in the past or is this a new cron job?</div><div><br>
</div><div>You might also try using the full path to ntpdate if you can't just run ntpd like others have suggested.</div><div><br></div><div><font color="#888888">-Tom</font><div><div></div><div class="h5"><br><br>On Apr 27, 2011, at 1:30 PM, David Champion <<a href="mailto:dchamp1337@gmail.com" target="_blank">dchamp1337@gmail.com</a>> wrote:<br>
<br></div></div></div><div><div></div><div class="h5"><div></div><blockquote type="cite"><div>I would agree, you should try to run ntpd instead of the cron job.<br><br>I have seen some systems (older RedHat) where ntpd wouldn't stay running, the system default was to run a cron task like yours. Seems like a band-aid fix.<br>
<br>If you want to fix the cron, try putting the full path to the binary in the cron entry, since cron doesn't have any environment settings like you do when you run commands from the shell.<br><br>-dc<br><br><div class="gmail_quote">
On Wed, Apr 27, 2011 at 1:24 PM, Aaron Porter <span dir="ltr"><<a href="mailto:atporter@gmail.com" target="_blank"></a><a href="mailto:atporter@gmail.com" target="_blank">atporter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>On Wed, Apr 27, 2011 at 11:19 AM, Tim Champion <<a href="mailto:timchampion@gmail.com" target="_blank"></a><a href="mailto:timchampion@gmail.com" target="_blank">timchampion@gmail.com</a>> wrote:<br>
> I have the following line in cron that seems to not ever run.<br>
><br>
> 46 03,11,19 * * * ntpdate -s <a href="http://0.north-america.pool.ntp.org" target="_blank">0.north-america.pool.ntp.org</a><br>
><br>
> If I run the ntpdate command alone, it works. I also fire off a backup<br>
> script that runs successfully daily, so I have no idea what's wrong here.<br>
<br>
</div>Have you checked syslog? You should get cron run logs & errors there.<br>
Also, if time is that important to you, why not run ntpd?<br>
_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org" target="_blank"></a><a href="mailto:Cialug@cialug.org" target="_blank">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank"></a><a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</blockquote></div><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Cialug mailing list</span><br><span><a href="mailto:Cialug@cialug.org" target="_blank">Cialug@cialug.org</a></span><br>
<span><a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a></span><br></div></blockquote></div></div></div><br>_______________________________________________<br>
Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
<br></blockquote></div><br>