Page MenuHomeFreeBSD

newsyslog(8): Add support of specifying compression method in configuration file.
ClosedPublic

Authored by delphij on Dec 25 2023, 7:54 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 8, 8:36 PM
Unknown Object (File)
Oct 24 2024, 8:25 AM
Unknown Object (File)
Oct 22 2024, 12:22 PM
Unknown Object (File)
Oct 21 2024, 6:28 PM
Unknown Object (File)
Oct 21 2024, 6:28 PM
Unknown Object (File)
Oct 21 2024, 5:00 PM
Unknown Object (File)
Oct 19 2024, 11:21 PM
Unknown Object (File)
Sep 28 2024, 5:15 AM

Details

Summary

Administrators can now specify a global compression method directly
at the beginning of the newsyslog.conf file, for example:

<compress> none

MFC after: 1 week

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

delphij created this revision.

Will it be possible to use legacy settings and compress logs using different tools, for example, some files with bzip2, others with xz and a few with zstd ?

I suppose it will work with
<compress> legacy
what I hope will be the default

This seems to correspond to the recently added command line option: -c

This revision is now accepted and ready to land.Dec 25 2023, 11:33 AM

I think this is a step in the right direction (having the compression specified in the config file), but I think it needs better integration with the existing flags. For example, there could be a new flag selecting the default as specified with <compress>, replacing J in the default config file lines.

netchild added inline comments.
usr.sbin/newsyslog/newsyslog.c
524

I agree with the classification in the email thread about "legacy" being a time variant classification. What about "pre15" or "v1" or "perlog" (as in "apply the compression settings as specified per log file compression flag") instead?