Am Mittwoch, 2. Dezember 2020, 17:10:20 CET schrieb Thorsten Kukuk:

> > the first thing i do on a server is to disable systemd-journal and use

> > logrotate.

>

>

> logrotate does not write any logfiles, it moves them away if they get to

> big.

> So I assume, you disable systemd-journal and use a syslog implementation

> instead?

> Doesn't change anything on the picture, applications run via systemd

> service  files still log to stdout/stderr and not in their log file.

Of course syslog.

I know that.

And you don't have to make all people stupid here.

> > How are you going to look for a bug in the log if you don't know exactly

> > what  to look for?

optical pattern

> Sorry, I don't understand. I don't see a difference in filtering a file

> or the journalctl output.

>

>

> > So you're just looking for a pattern in the log.

> >

> > That doesn't work with systemd.

>

>

> Of course it works? I do that all the day.

>

>

> > This only works with text files.

>

>

> journalctl output is pure ascii text?

>

>

> > And so systemd-journal is completely pointless for servers.

> >

> >

> > Please let it enable.

>

>

> I don't want to disable anything, it is already disabled since a

> very long time.

> The output to log files is disabled in 99% of the packages who creates

> files or directories in /var/log I looked at.

>

> Seems like you mix up journald, syslogd, logrotate and applications

> creating their own log files.

I don't use journal.

It's to slow to search.

Not searchable for optical pattern.

And i install always on server syslog and logrotate.

REgards