Re: [Netatalk-devel] Feedback Request: Microsecond time stamp logging

[Hauke F. <ha...@Es...>]

On Fri, 15 Dec 2023 09:00:33 +0000, Daniel Markstedt wrote:
> When you log to a file (the "log file" option), netatalk is hard 
> coded to output a time stamp in this format: Dec 08 15:59:35.402141
> 
> However, it has recently been reported by a user that the microsecond 
> granularity is causing incompatibility with a particular log 
> management solution that they are using.

Well, my knee-jerk reaction: Netatalk shouldn't have to adapt to an 
inflexible, effectively borken log parser.

> In addition, I think the microsecond logging clutters the logs.

Run the log through sed(1) if you want the microseconds cut out?

> It's worth noting that Netatalk logs with second accuracy to syslog 
> by default on all systems I've looked at (probably controlled by a 
> system level log daemon?)

That's syslogd (on my NetBSD machine, at least ;) providing the time 
stamps.

The bug reporter is talking about having netatalk log to a *file*, in 
which case it provides its own timestamps.
 
> Off the top of my head, I can think of one reason for microsecond 
> accuracy: Fine-grained performance profiling.

With faster machines, more things happen within a second. When the 
events reported happened at distinctly different times, it makes a lot 
of sense to provide the exact time stamp.

My 0.02 EUR,
Hauke

-- 
Hauke Fath                        <ha...@Es...>
Linnéweg 7
64342 Seeheim-Jugenheim
Germany