From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 21A381381F3 for ; Fri, 26 Apr 2013 15:54:39 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8D165E0AA8; Fri, 26 Apr 2013 15:54:32 +0000 (UTC) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 167DBE0933 for ; Fri, 26 Apr 2013 15:54:30 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id es20so3742776lab.13 for ; Fri, 26 Apr 2013 08:54:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=Wu/ELGTp27x4vuME0Z2QhIqJCRIzcka71sokuvB5y7o=; b=Jr8MUm11E7qTiVza/JawLcrxCq1zurZ4kbkc8LQC1wQxpHrPt2bNPGtPhV0I/oKIOy ZCTDkMOUROv2Dh92UuR1WHdgdH2h0Z4h/MXORe+yUY5ZBYrbZ+T+AR16TuubITuiWGkO oovX23ABWRgCHSpgxofPl0QzXRpzonIhmJGGaL9oK/d645gsL3wqmxkfayXUlA8QxoQm gp7i00+DKRMuIHAYKuglKcDEsf7XNTDwMsOqGzUkNAdTvblDHrmVdbMhgA2b4UxJGMde GNIKuw1TvlevQw84Qi+d4BiAlQHr9tVK4pZfE+YWwertx1Bt34wU71PJdeXk3NgaMru+ 0O8A== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.160.105 with SMTP id xj9mr22026291lbb.87.1366991669277; Fri, 26 Apr 2013 08:54:29 -0700 (PDT) Received: by 10.114.48.40 with HTTP; Fri, 26 Apr 2013 08:54:29 -0700 (PDT) In-Reply-To: <517AA020.2070805@gmail.com> References: <20130426141011.GH24932@syscon7.inet> <517A949D.6030800@gmail.com> <517AA020.2070805@gmail.com> Date: Fri, 26 Apr 2013 11:54:29 -0400 Message-ID: Subject: Re: [gentoo-user] Server system date synchronizaion From: Nick Khamis To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 50f4fd24-81c6-46a5-8490-9595257c470c X-Archives-Hash: ee6ede073c56fbfa77cf7d182d4cd4d0 On 4/26/13, Alan McKinnon wrote: > On 26/04/2013 17:27, Nick Khamis wrote: >> Hello Everyone, >> >> Thank you for the many solutions however, I am totally lost as to which >> would >> be most reliable in a collocation setting vs. office desktop. What we >> would like >> is to set up our own ntp server which other servers and desktops in our >> office >> syncs to. Is this advised? If so, is there a nice tutorial online? > > The subject of time is vastly more complex than anyone ever thinks at > first look. Time servers are tiered and are themselves both clients and > servers... > > So here's what you do: sync everything to your ISP's time servers. > Chances are good they do a better job than you can, just like with DNS > caching. > > When you know more about the subject than you do now, you can venture > into rolling your own. I'm not being rude or funny - time servers are > just one of those things that unless you have special needs and LOTS of > cash, it is so much easier to just let someone else do all the heavy > lifting. > > > -- > Alan McKinnon > alan.mckinnon@gmail.com > > > Hello Alan, Thank you so much for your response, and I totally understand the effort vs. benefit challenge. However, is it really that much trouble/unstable to setup our own ntp server that syncs with our local isp, and have our internal network sync on it? N.