On Sunday, July 6, 2025 10:27:17 AM Pacific Daylight Time Hal Murray wrote:
> Interesting. Thanks.
>
> > Currently it adds 16 bytes per line logged.
>
> I think 16 is a bit too much.
>
> > The code is pretty simple and I think it should be portable.
> > + fprintf(term_fil
Interesting. Thanks.
> Currently it adds 16 bytes per line logged.
I think 16 is a bit too much.
> The code is pretty simple and I think it should be portable.
> + fprintf(term_file, "%s[%d.%ld]: ", prog, pid,
> (long int)pthread_self());
The Linux man page says that
On Saturday, July 5, 2025 10:40:16 PM Pacific Daylight Time Hal Murray via
devel wrote:
> I'd like msyslog to indicate which thread is doing the logging.
>
> The main thread in ntpd currently creates up to 3 threads.
> One for DNS, and a NTS thread for each of IPv4 and IPv6.
> The DNS thread ge
Yo Hal!
On Sat, 05 Jul 2025 22:40:16 -0700
Hal Murray via devel wrote:
> I'd like msyslog to indicate which thread is doing the logging.
Nice idea.
> Anybody thought about this area? Any good ideas?
None from me, but I like your idea.
RGDS
GARY
--
I'd like msyslog to indicate which thread is doing the logging.
The main thread in ntpd currently creates up to 3 threads.
One for DNS, and a NTS thread for each of IPv4 and IPv6.
The DNS thread gets created and joined, but there is only one at any time.
We may need more NTS threads in the futur
