examples: handle more actions in NM dispatcher script
Run the chronyc onoffline command also when the connectivity-change and dhcp6-change actions are reported by the NetworkManager dispatcher. The latter should not be necessary, but there currently doesn't seem to be any action for IPv6 becoming routable after duplicate address detection, so at least in networks using DHCPv6, IPv6 NTP servers should not be stuck in the offline state from a previously reported action.
This commit is contained in:
parent
5bd13c8d59
commit
e55f174bd3
1 changed files with 12 additions and 2 deletions
|
@ -7,8 +7,18 @@ export LC_ALL=C
|
|||
|
||||
chronyc=/usr/bin/chronyc
|
||||
|
||||
# For NetworkManager consider only up/down events
|
||||
[ $# -ge 2 ] && [ "$2" != "up" ] && [ "$2" != "down" ] && exit 0
|
||||
# For NetworkManager consider only selected events
|
||||
if [ $# -ge 2 ]; then
|
||||
case "$2" in
|
||||
up|down|connectivity-change)
|
||||
;;
|
||||
dhcp6-change)
|
||||
# No other action is reported for routable IPv6
|
||||
;;
|
||||
*)
|
||||
exit 0;;
|
||||
esac
|
||||
fi
|
||||
|
||||
# Note: for networkd-dispatcher routable.d ~= on and off.d ~= off
|
||||
|
||||
|
|
Loading…
Reference in a new issue