On Wed, Jun 14, 2023 at 07:26:11PM +0900, Jongkyu Seok wrote:
> Based on your answer, it sounds like simply creating a link under the
> configured.d directory without any script modifications would solve the
> problem.
Does it work if you have the link only in the configured.d and off.d
I didn't want to respond too quickly and observe the situation...
The current setup uses the local raspberry (with attached GPS receiver)
as single source. This is the output from the server (public servers
just shown for comparison)
chronyc -m sources sourcestats tracking
MS Name/IP address
Hi,
I'm having a problem with a system configured as a stratum 1 NTP server,
running chrony, and I can't seem to be able to figure out what is happening and
what might be the root cause of the problem.
(details about the setup are at the end of this message)
Basically, my stratum 1 servers
[TL;DR]
1. networkd-dispatcher uses specific environment variables for passing
interface state. (https://gitlab.com/craftyguy/networkd-dispatcher#usage)
2. script file(or symbolic link) must be located in
/usr/lib/networkd-dispatcher/configured.d because 'chronyc onoffline'
command sets sources
On Wed, Jun 14, 2023 at 04:44:50PM +0900, Jongkyu Seok wrote:
> Because networkd-dispatcher uses specific environment variables to pass
> interface state, nothing exists in the shell argument of dispatcher script.
>
> Because of this, the '[ $# -ge 2]' condition in the existing
>
Thank you for answering.
> I don't follow. Doesn't the routable state follow configured? Why
> would it need to be called twice?
> Do you have an example sequence of the events?
Below is log of the networkd-dispatcher environment variables when the
20-chrony script(linked in the routable.d &
