[SOLVED] MGA3 - Where is syslog?

[Myles]

This may sound a bit stupid to all of you more knowledgeable folk, but where is syslog in Mageia #3?

In Mageia #2 I went into syslog from here (root/var/log/syslog) (via Dolphin). Screen dump of Mageia #2 syslog location - http://i1099.photobucket.com/albums/g391/Myles5712/Mageia%203%20Problems/Dolphinshowingsyslogfile_zps0094ef96.png
After doing a complete install of Mageia #3 (see other post in forum regarding upgrade/install problems). That went well – well the install part went well not anything else! I have had the system problems since re-installing! And, when my system has failed, I re-boot, logon and go to where “syslog” used to be (root/var/log/syslog) and it isn’t there! Screen dump of Mageia #3 syslog location - http://i1099.photobucket.com/albums/g391/Myles5712/Mageia%203%20Problems/Nosyslogfile_zpsf608500d.png. Neither are a lot of logs it seems that used to to be there in Mageia # 2, so I don’t know why my system has failed! Am I missing something? Have the logs moved to another location? Have I done something wrong in the install?

[djennings]

In mga3 syslog is replaced with journalctl. See the thread

viewtopic.php?f=7&t=5249

Install the rsyslog package to get the old behaviour.

[srtxg]

you can install "rsyslog" package if you want old syslog.

but in Mageia3 systemd is used, which has it's own journal system (which has more potential tha old syslog).
you can see journal entries with "journalctl".
see the man page for journalctl for the various options.

when you look at the status of a service (eg: systemctl status foo.service) it tells also very interesting info; current running status of the service daemons and childrens and the last log messages.

"journalctl -p <somelevel>" will output the syslog messages for a given level (the numeric values used by syslog); the main difference is that in syslog you can redirect to different files based on level/service; wile in journalctl all is together, but you can filter at output.
"journalctl -u <servicename.service>" will show the log messages for the given service.

(add "[SOLVED]" to the subject if that info solves your issue; thanks)

[Myles]

Thanks for that info. My bad, I should have searched for syslog as a topic and I would have found the thread.
And yes, I did suspect that the journal folder may have had something to do with syslog (Ipresume that is wher this journalctl lives/writes?
I'll have to have a look at what it does and see how I go.

[doktor5000]

Check http://0pointer.de/blog/projects/journalctl.html

[Myles]

Thanks for that doktor5000, more reading to do so I can get a handle on all this. I used to be technical (Windows) but have lost the edge over the last few years and I am now retired. I had heard of systemd but never really knew what it was exactly, I knew that is was pretty low-level system stuff.
Anyway, off to read the journalctl man pages and the blog.

[doktor5000]

The blog is actually better than the man pages, written by the author of systemd and journalctl