On 23/03/20 10:58, Stefan Raspl wrote: > Thx! > As for SIGHUP: The problem that I see with logrotate and likewise approaches is > how the heading is being handled: If it is reprinted every x lines (like the > original logging format in kvmstat does), then it messes up any chance of > loading the output in external tools for further processing. > If the heading is printed once only, then it will get pushed out of the log > files at some time - which is fatal, since '-f <fields>' allows to specify > custom fields, so one cannot reconstruct what the fields were. For CSV output, can't you print the heading immediately after SIGHUP reopens the files? (Maybe I am missing something and this is a stupid suggestion, I don't know). Paolo > That's why I did things as I did - which works great for .csv output. > I'd really like to preserve the use-case where a user has a chance to > post-process the output, especially .csv, in other tools. So how how about we do > both, add support for SIGHUP for users who want to use logrotate (I imagine this > would be used with the original logging format only), and keep the suggested > support for 'native' log-rotation for .csv users?
