Re: [chrony-dev] [PATCH] nm-dispatcher: handle NTP servers from DHCP |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [PATCH] nm-dispatcher: handle NTP servers from DHCP
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 8 Jun 2020 16:53:37 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1591628024; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OwC8AGoT3A+0hc48MspWLiK5KkXG0gxS2/v/6lJGJk4=; b=Oh/dV2UWk03RYix2yfoxFc5GHCGPf706rrjATCihMlRL7yGaDQU9+wChcYNpTzfT6o3oh0 lZNpV1OBCJVxHxqUEPd4x401OCfvOWLkgGTO6yf7mTiXv5eKOLgJ+EAUAjTZ/cUlahARJD 4E/wsaLYtG3EaLwkfSBITvXYZPDHr+U=
On Fri, Jun 05, 2020 at 06:23:21PM -0400, Robert Fairley wrote:
> On Thu, May 28, 2020 at 5:44 AM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> > I suspect this breaks the networkd-dispatcher support. IIRC there are no
> > arguments passed to the script.
>
> I see - I should have looked into what'd happen if less than 2
> arguments were passed. Reading on networkd-dispatcher - I think to
> best preserve compatibility of the original chrony.nm-dispatcher
> file (e.g. so downstreams using networkd-dispatcher don't need to
> patch the file), the DHCP bits should be kept in a separate
> dispatcher script. I updated the patch to instead add
> `chrony.nm-dispatcher.dhcp.in`. That way, `chrony.nm-dispatcher.dhcp`
> (after substituting macros) can be packaged downstream as
> `/usr/lib/NetworkManager/dispatcher.d/20-chrony-dhcp` or so, or
> ignored if not using NetworkManager.
Good idea.
Would it make sense to add a suffix to the non-DHCP dispatcher script
(e.g .online -> 20-chrony-online) to avoid confusion with the two
scripts?
Also, could you please rename the default_options variables in the
helper and dispatcher scripts to something like default_source_options
or default_server_options to make it more clear where the options are
used?
Thanks,
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.