[chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.2-22-gfca8966 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The branch, master has been updated
via fca8966adaaf8376536af86ba2afe02501463588 (commit)
via 25f80a1a9d134e37173ab7f8a2c0d822e75fd2e1 (commit)
from 1219f99935ca9597eb0e4f4c6039e536462cf1a6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit fca8966adaaf8376536af86ba2afe02501463588
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Wed Mar 23 15:17:03 2022 +0100
examples: replace grep command in NM dispatcher script
Some grep implementations detect binary data and return success without
matching whole line. This might be an issue for the DHCPv6 NTP FQDN
check. The GNU grep in the C locale seems to check only for the NUL
character, which cannot be passed in an environment variable, but other
implementations might behave differently and there doesn't seem to be a
portable way to force matching the whole line.
Instead of the grep command, check for invalid characters by comparing
the length of the input passed through "tr -d -c".
commit 25f80a1a9d134e37173ab7f8a2c0d822e75fd2e1
Author: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Date: Wed Mar 16 14:46:13 2022 +0100
doc: include gnutls in libraries providing SECHASH feature
-----------------------------------------------------------------------
Summary of changes:
doc/chrony.conf.adoc | 2 +-
doc/installation.adoc | 2 +-
examples/chrony.nm-dispatcher.dhcp | 6 +++++-
3 files changed, 7 insertions(+), 3 deletions(-)
hooks/post-receive
--
chrony/chrony.git
--
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.