Comments for ByteChemist http://www.bytechemist.com Sun, 18 Oct 2009 22:56:06 +0000 http://wordpress.org/?v=2.9.1 hourly 1 Comment on Use cron and ntpdate to keep your linux server’s time updated by CHEMiST http://www.bytechemist.com/2009/06/25/use-cron-and-ntpdate-to-keep-your-linux-servers-time-updated/comment-page-1/#comment-500 CHEMiST Sun, 18 Oct 2009 22:56:06 +0000 http://www.bytechemist.com/?p=27#comment-500 Good point. My suggestion is to run ntpdate on a weekly basis. The second cron was simply an example but could have been misleading. I've updated the post to clear up any confusion. Really appreciate the feedback, I'll give ntpd a dig. Good point. My suggestion is to run ntpdate on a weekly basis. The second cron was simply an example but could have been misleading. I’ve updated the post to clear up any confusion.

Really appreciate the feedback, I’ll give ntpd a dig.

]]> Comment on Use cron and ntpdate to keep your linux server’s time updated by Shane Bishop http://www.bytechemist.com/2009/06/25/use-cron-and-ntpdate-to-keep-your-linux-servers-time-updated/comment-page-1/#comment-499 Shane Bishop Sat, 17 Oct 2009 07:35:30 +0000 http://www.bytechemist.com/?p=27#comment-499 Please don't tell people to run ntpdate via a cronjob. If it's just once a week, fine. But especially don't recommend doing it every 15 minutes. It's a frequent bone of contention for ntp server operators, because people doing this causes floods of ntp traffic all at once. That in turn causes the time returned by the server to be less accurate than it could be, and therefore less useful to the users in the long run. Instead, people should be running ntpd. On Ubuntu, this is as simple as installing the ntp package (the default config is fine for most folks). It picks random intervals to sync time, and can also compensate for regular clock skew, avoiding large jumps in time if you have a particularly bad clock. It is also very lightweight for those who are paranoid about having yet another process running on their computers. Please don’t tell people to run ntpdate via a cronjob. If it’s just once a week, fine. But especially don’t recommend doing it every 15 minutes. It’s a frequent bone of contention for ntp server operators, because people doing this causes floods of ntp traffic all at once. That in turn causes the time returned by the server to be less accurate than it could be, and therefore less useful to the users in the long run.

Instead, people should be running ntpd. On Ubuntu, this is as simple as installing the ntp package (the default config is fine for most folks). It picks random intervals to sync time, and can also compensate for regular clock skew, avoiding large jumps in time if you have a particularly bad clock. It is also very lightweight for those who are paranoid about having yet another process running on their computers.

]]> Comment on Using Rsync over SSH by CHEMiST http://www.bytechemist.com/2008/01/10/using-rsync-over-ssh/comment-page-1/#comment-491 CHEMiST Wed, 12 Aug 2009 18:24:47 +0000 http://www.bytechemist.com/2008/01/10/using-rsync-over-ssh/#comment-491 Thanks Kelly, appreciate the feedback! Thanks Kelly, appreciate the feedback!

]]> Comment on Using Rsync over SSH by Kelly Brown http://www.bytechemist.com/2008/01/10/using-rsync-over-ssh/comment-page-1/#comment-480 Kelly Brown Fri, 12 Jun 2009 19:14:23 +0000 http://www.bytechemist.com/2008/01/10/using-rsync-over-ssh/#comment-480 Hi, very nice post. I have been wonder'n bout this issue,so thanks for posting Hi, very nice post. I have been wonder’n bout this issue,so thanks for posting

]]>