Re: NTP signd socket status logging enhancement
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZS0zvhPZ5nDw6/wV@localhost> |
On Thu, Oct 05, 2023 at 11:01:45AM -0400, Jeremy Jackson wrote: > Perhaps gentler wording would be appropriate? If not, I guess sysadmin could infer the same thing from the lack of a connection success message. I guess I could also filter out the case of an existing unix socket, with proper permissions, that just isn't accepting connections, from all the other error conditions, that aren't dependent on state of Samba running or not. I'd suggest to only log errors, not successes, and only once between successful connections. > I suppose if Samba failing and recovering quickly being the cause of log flooding is a concern, a rate limit could be set? But it seems like there are bigger problems if that is the case. Fair enough. > The general principle I'm aiming for, is that problems due to samba not running, permission errors, config file errors, should be made obvious, and shouldn't require tcpdump, debug logs, reading source code, and other low level approaches. Yes, that makes sense to me. > Stil, it's pretty nice to have a working NTP that requires zero config for Windows clients. I hope they will start using NTS and this signd hack can be dropped eventually. -- Miroslav Lichvar -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]