all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] services: ntpd: Make large clock adjustments if necessary.
Date: Thu, 13 Oct 2016 10:12:46 -0400	[thread overview]
Message-ID: <20161013141246.GA7431@jasmine> (raw)
In-Reply-To: <20161013050650.GA25727@jocasta.intra>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Thu, Oct 13, 2016 at 07:06:50AM +0200, John Darrington wrote:
> I think that this should be a configuration item in the service, so that the
> user can decide whether to have it or not.  I don't think we should force it
> on the user.   Some applications break if the clock makes large jumps.

I agree. This is really something that the system administrator should
evaluate and fix on a case-by-case basis.
  
> The ntpd authors decided that the default behaviour is not to make large jumps
> so I think we should respect that unless there is a good reason to do otherwise.
> So I think this should be configurable in /etc/config.scm and the default should
> be not to use -g

For me, I have to do this so rarely (and never on the machines I
currently use) that I am fine with having to run `ntpd -g ...` by hand.

So, if we want to make this configurable in the OS configuration,
volunteers are welcome to work on it :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-10-13 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 23:21 [PATCH 1/1] services: ntpd: Make large clock adjustments if necessary Leo Famulari
2016-10-13  5:06 ` John Darrington
2016-10-13 14:12   ` Leo Famulari [this message]
2016-10-19 20:49     ` Ludovic Courtès
2016-10-19 21:39       ` Leo Famulari
2016-10-20 19:44         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161013141246.GA7431@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.