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 C9D1413877A for ; Mon, 28 Jul 2014 21:20:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A6727E0C4D; Mon, 28 Jul 2014 21:20:13 +0000 (UTC) Received: from postler.lichtfels.com (postler.lichtfels.com [78.46.92.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7751EE0C34 for ; Mon, 28 Jul 2014 21:20:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by postler.lichtfels.com (Postfix) with ESMTP id AE2C3125CA for ; Mon, 28 Jul 2014 23:20:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xunil.at; s=mailout; t=1406582409; bh=QWXxJpiILRdz0qEokgVriq/IxXhGPSRppfPhxCoXMOw=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=QqT9/8Gnzp0R8b1PCCMvGcjMrPXIiPm9nx1W5vMS4CCTc7fCxRZqAis29XE78Rn+C gM2JtJGIqk8h7xHM0lnlEgM9sP4oAE2YH2wHecDiobZYvXTjO80jTH/1yoSrr+D0Vq ixVUa1aUYBuXfvxRpGT8CqHUEk5NpjbcXvjYGz9A= Received: from postler.lichtfels.com ([127.0.0.1]) by localhost (postler.lichtfels.com [127.0.0.1]) (amavisd-maia, port 10024) with LMTP id 19351-02 for ; Mon, 28 Jul 2014 23:20:07 +0200 (CEST) Received: from hiro.oops.intern (unknown [IPv6:2001:15c0:65ff:8742:35f9:f3c4:2c44:512a]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by postler.lichtfels.com (Postfix) with ESMTPSA id 74294123C9 for ; Mon, 28 Jul 2014 23:20:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=xunil.at; s=mailout; t=1406582407; bh=QWXxJpiILRdz0qEokgVriq/IxXhGPSRppfPhxCoXMOw=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=Ih8UIQhP5sDwL228x5wYbp9NHq6blaz2z1RWflz4ac0gPWDHRUgkzhik6wz8lcUki isiGcHSyNcZkLe3yC0ggjzR1XzCTiSwjDImWW3p06rtRvPKIRijKqDZh9o+CToTerj 9MoVzdyjiZKqzt9n/Eqylc/jBQZtgxUvPFZaMXOg= Message-ID: <53D6BE86.8030408@xunil.at> Date: Mon, 28 Jul 2014 23:20:06 +0200 From: "Stefan G. Weichinger" Organization: oops! User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] re: which NTPd package to use? References: <53D39983.8050706@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.2c X-Archives-Salt: 96426d45-f926-46d0-9e49-6306c83807b2 X-Archives-Hash: 13fc1358847b2cb76942f9ec2472113b Am 28.07.2014 18:47, schrieb Rich Freeman: > Anybody have a decent comparison of timedated vs ntpd or anything else > for that matter? > > Running ntpd isn't hard at all, so I'm not really sure why I'd want to > switch. At the very least I'd want to ensure that the replacement > covers the basics. > > I am running networkd and I'm very happy with it. Setting it up for > dhcp-only is brain-dead simple, and I have it serving up a bridge for > containers/kvm with fairly little trouble as well. AFAI understand it the systemd-timedated.service helps setting clock and time-related settings ... and if you use it to enable NTP syncing, systemd-timesyncd.service will actually take over the part of syncing with ntp servers. I also preferred chrony over ntp for the last year or so. Better with laptops etc. and quicker to correct time when there is large offset. What I haven't yet fully understood: daemons like chrony bring a specific settings file for systemd-environments, in this case: /usr/lib/systemd/ntp-units.d/50-chrony.list (saying "chronyd.service") In the same directory I see 90-systemd.list (saying "systemd-timesyncd.service"). As far as I understand this: if other ntp-software is installed, systemd-timedated.service uses the ntp-unit with higher priority (in my current case chronyd.service) for ntp-syncing. So you may use the systemd-timedated.service to do your settings and in the same setup let it use another ntp-daemon to actually do the syncing behind the curtains. Generalized interface with choice --- nice, isn't it? ;-) but maybe I misunderstand. Stefan