| Re: [chrony-users] NTP signd socket status logging enhancement |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] NTP signd socket status logging enhancement
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 5 Oct 2023 15:23:44 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696512227; 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=OqDNRgCLJ9wOlj1KQBpJdW+GJbq9GFbg9BgscObfclc=; b=ATjiDQzCR1EutJhrjMhvKB67GdrxjqhCiUtX6cJnZvF4KkpkBkga0Byvz70GlcEQIkNOod mzrombO95CqoM55qSxk5oYvrNC233aRcpVuNy84fHP03nQyuQPrhit7KEkOfbb5OA20sNd EGgl59jhAWPu5FeyWAwypRWoOYcHjiA=
On Wed, Oct 04, 2023 at 08:42:10AM -0400, Jeremy Jackson wrote:
> https://gitlab.com/chrony/chrony/-/merge_requests/3
>
> I spent longer than I should have troubleshooting a typo in a config file, so I thought I'd contribute a logging enhancement that could save others (including my future self, heh) some time.
>
> Transitions in status of running Samba AD process are also reflected in log messages.
I think that reported error in the initial connection could be
confusing to users as chronyd is normally not ordered in the boot
after samba and would likely be failing.
Requests from clients shouldn't be able to trigger an informational
log message to avoid flooding the syslog. There already is an error
reported for failed connect as a debug message.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.