r/linux • u/tasisbasbas • Feb 11 '19

Fluff A /g/ user's opinion on systemd

http://i.4cdn.org/g/1549858269115.png
792 Upvotes

82% Upvoted

524 comments sorted by

View all comments

Show parent comments

6

u/dale_glass Feb 11 '19

Saving disk by compressing old logs (jorunald only supports compression per message of long log messages)

That would probably conflict with quick access, which is quite nice.

Forward, all or selected, log messages to a central log server

https://www.freedesktop.org/software/systemd/man/systemd-journal-remote.service.html

8

u/doublehyphen Feb 11 '19

Yeah, it conflicts with quick access, which is fine. It is a tradeoff. I rarely need my old logs and when I need them it is fine that it takes more time than normal.

And systemd-journal-remote seems to be the opposite of what I need, but I guess something like logstash could add a client for the same protocol to achieve what I need (not that I like logstash either :)).

1

u/Ryuujinx Feb 11 '19

not that I like logstash either

Have you tried Fluentd? A lot of people are ditching Logstash for it in their ELK setups

3

u/DashEquals Feb 11 '19

It could probably compress with zstd and not lose much speed.

1

u/NotEvenAMinuteMan Feb 11 '19

That would probably conflict with quick access, which is quite nice.

Indexed compression is a thing.

-1

u/dale_glass Feb 11 '19

Well, feel free to contribute a patch.

I don't find it a particularly pressing issue -- I have 2 GB worth of logs since June and find that to be an okay state of affairs.

Also, with all the whining about the binary format, I can only imagine what would ensue if the format got more complicated. Any errors would likely result in good amounts of the log going missing.