#21 2017-06-01 13:38:00

Steve

Member

Registered: 2017-01-03

Posts: 642

Re: Journalctl and Journaling on by Default?

Would i be correct on reading "man syslogd"

http://ftp.ics.uci.edu/pub/centos0/ics- … slogd.html

Looks like i can forward journald to syslog via /etc/systemd/journald.conf

Last edited by Steve (2017-06-01 13:38:49)

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: Journalctl and Journaling on by Default?

Wanting to limit my journalctl using

sudo journalctl --vacuum-time=2days

That option only became available with version 227 of systemd, you will have to use /etc/systemd/journald.conf instead.

Why would you want to replace the systemd journal?

It's the best logging mechanism around, IMO.

---

Para todos todo, para nosotros nada

Steve

Member

Registered: 2017-01-03

Posts: 642

Re: Journalctl and Journaling on by Default?

Thankyou for the explanations. More curiosity/general education than anything else Hoas.

Cheers

KrunchTime

Member

Registered: 2015-09-29

Posts: 857

Re: Journalctl and Journaling on by Default?

my /var/log/journal currently holds 2.6GB

Restrict the maximum size in /etc/systemd/journald.conf

For stretch, you can "vacuum" away excess journal contents

According to the article below, look for and change one or more of the following:

SystemMaxUse
SystemKeepFree
SystemMaxFileSize

For me, the question is what was wrong with rsyslog.

Ducks...

Linux Magazine had a great article in the Aug 2017 issue on using journalctl to evaluate systemd logs.  I'll quote what the author said:

The journald daemon not only records much more data than other logging mechanisms, but actually starts up much earlier in the boot process than was previously possible.  This is a huge help when narrowing down system startup problems. ... As soon as you've come to grips with the journald daemon, you'll never want to go back to a time before systemd.  The logs are not only more detailed, but start much earlier during system boot.  They're both more comprehensive and easier to analyze.

Last edited by KrunchTime (2017-08-09 08:59:35)

Horizon_Brave

Operating System: Linux-Nettrix

Registered: 2015-10-18

Posts: 1,473

Re: Journalctl and Journaling on by Default?

my /var/log/journal currently holds 2.6GB

Restrict the maximum size in /etc/systemd/journald.conf

For stretch, you can "vacuum" away excess journal contents

According to the article below, look for and change one or more of the following:

SystemMaxUse
SystemKeepFree
SystemMaxFileSize

For me, the question is what was wrong with rsyslog.

Ducks...

Linux Magazine had a great article in the Aug 2017 issue on using journalctl to evaluate systemd logs.  I'll quote what the author said:

The journald daemon not only records much more data than other logging mechanisms, but actually starts up much earlier in the boot process than was previously possible.  This is a huge help when narrowing down system startup problems. ... As soon as you've come to grips with the journald daemon, you'll never want to go back to a time before systemd.  The logs are not only more detailed, but start much earlier during system boot.  They're both more comprehensive and easier to analyze.

My thoughts exactly... but who listens to little 'ol me?

---

"I have not failed, I have found 10,000 ways that will not work" -Edison