Sergey G. Brester

> what is needed to get 1.1.1 released? Time. But I'd also like to close few issues - #3999 (+ #4030) and possibly #3917

> you are invited to this repository. Thx! > I would like to have sth. like this branches 1. agree 2. unsure I understand correctly the purposes or else the...

Since this PR looks good for us, merged now to master. Thx! As for the branches and multiple releases, I don't see why we may need it. Are not the...

> By becoming such a destination itself, fail2ban can start receiving the datagrams directly -- without the need to monitor log-files and associated latencies and resource-consumption. Questionable that it'd be...

> I noticed there is no space between the value and the string "dbpurgeage" in the output. Looks intentional to me: `86400seconds` is the same than `86400s` or `24hours` (`24h`)...

> Journal identifier or unit name : current is `[email protected]` Well, #3692 shows that current is `_SYSTEMD_UNIT=postfix.service [email protected]`, so what would we need here? `_SYSTEMD_UNIT=postfix.service _SYSTEMD_SLICE=system-postfix.slice` or rather `_SYSTEMD_SLICE=system-postfix.slice` ?

> I belive Zstd supports this format in the standard, but its up to the compressor to use it. Well, not really... Seekable format is something like PoC, that was...

> it is a problem to have for both .zstd single files and containers for like .7z and .zip? It is not a problem for .7z too (no idea about...

You could add it to Parameters like here: 

As the libsystemd' [documentation](https://manpages.debian.org/stretch-backports/libsystemd-dev/sd_journal_wait.3.en.html#NOTES) says: > All functions listed here are thread-agnostic and only a single specific thread may operate on a given object during its entire lifetime. It's safe...