Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi,
i like to see if i understood.
rsyslogd write in /var/log/messages,/var/log/secure so on and systemd-journald write in /var/log/journal if Storage=persistent.
somehow systemd-journald uses rsyslogd to write in /var/log/messages?
Feb 18 06:35:34 Razan1 systemd: Starting The Apache HTTP Server...
in /var/log/journal i can have more data as in /var/log/messages.corect?
I think the way it works is that journald makes available a socket, and syslogd and klogd can take their messages from there. They run as independent daemons; journald doesn't run them.
The journal contains the same information as /var/log/messages, but it also contains a lot of meta-information that allows the journalctl program to identify entries and print them out selectively on command. So, for example, you can look at the messages relevant to a particular service that is giving trouble, without having to scroll through a lot of other bumf. The price you pay of course is that the journal is a binary file and you can't inspect it with the usual text tools, only with journalctl.
hazel's explanation is correct, but RHEL and friends have a different approach. They read from the journal file directly, using a special rsyslogd module. The statement "only journalctl can read the journal" is, therefore, not quite correct.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.