3 ms·
My answer may not be satisfying, as I was never much of an init guru - never bothered much with configuration. But here are my systemd observations: - log fil
by rhn_mk1 9y ago
My answer may not be satisfying, as I was never much of an init guru - never bothered much with configuration.
But here are my systemd observations:
- log files now are binary and accessed by `journalctl` - it's a bit less convenient than looking for text files in `/var/log`
- unit files are a miracle. For the 7 or so years before systemd, I wrote one unportable init script, and I hated it. Now I churn them out whenver I feel like it - they are standardized and the docs are incredible.
Apart from that, nothing really changed from my POV, and I use systemd on desktop as well as in small servers.
- dylan-m 9y agoFor the log files, one miraculous thing you can do is `sudo journalctl -f -u httpd -u mariadb`, which watches the log for both of those services (and should output messages in the correct order). On a desktop, the way it's designed should make the system log viewer (if you need it) quite a bit faster and cleverer, since the stuff we used to do with grep or with extra tooling is just kind of built in to the format.
- duskwuff 9y agoAnother handy set of tools are the time-based queries, like "journalctl --boot" for logs since the last reboot, or "journalctl --since 16:30" to see logs since that time. (Which can also be specified in relative terms, like "-30m" for the last half hour.)
- TheDong 9y agoTo add on another handy trick, `journalctl -o cat` or `-o short` will output less information. It's a simple thing, but it's something I use quite often and I don't think everyone knows.
- jle17 9y ago> - it's a bit less convenient than looking for text files in `/var/log` I find it more practical to be able to filter logs in any way I want (get everything that concerns this device or this service or this user) rather than in a single way.