Okay, so how do I disable journald and switch to something else, without getting rid of systemd completely?
I just set the storage to volatile and the max log size to 10Mbytes and call it a day.
Logs are really only useful at the tail.
Having the previous boot can get you out of a hole if you're dealing with dodgy drivers.
So change it back when you have a dodgy driver to deal with
Put the following in etc/systemd/journald.conf.d/discard.conf
[Journal] Storage=none ForwardToSyslog=no ForwardToKMsg=no ForwardToConsole=no ForwardToWall=no
systemctl restart systemd-journald
https://www.freedesktop.org/software/systemd/man/latest/syst...
See StandardOutput= and StandardError=.
Ok, so I should set these to null? I saw elsewhere someone set journald storage to volatile. Which of these approaches is better?
> Oh no! Bad Request > Error: access denied: error in challenge meta-refresh: mismatched token
God I hate the modern web. I get that anti-bot measures are necessary, but at what cost?
You get the exact same information in
$ man systemd.exec
Though reading the question again, I should have probably linked to the equivalent of
$ man systemd-system.conf
as well, that's where you can set the default behavior across systemd, not per-service as the first man page is.
[dead]
On Debian, install rsyslogd instead - it's that simple.
I just set the storage to volatile and the max log size to 10Mbytes and call it a day.
Logs are really only useful at the tail.
Having the previous boot can get you out of a hole if you're dealing with dodgy drivers.
So change it back when you have a dodgy driver to deal with
Put the following in etc/systemd/journald.conf.d/discard.conf
Then restart withhttps://www.freedesktop.org/software/systemd/man/latest/syst...
See StandardOutput= and StandardError=.
Ok, so I should set these to null? I saw elsewhere someone set journald storage to volatile. Which of these approaches is better?
> Oh no! Bad Request > Error: access denied: error in challenge meta-refresh: mismatched token
God I hate the modern web. I get that anti-bot measures are necessary, but at what cost?
You get the exact same information in
$ man systemd.exec
Though reading the question again, I should have probably linked to the equivalent of
$ man systemd-system.conf
as well, that's where you can set the default behavior across systemd, not per-service as the first man page is.
[dead]
On Debian, install rsyslogd instead - it's that simple.