How would I get all outputs of systemd managed python2 script instantly into journal, just like it appears in terminal
I’ve created a systemd service to run a tomcat application based on the information found in this article. The short version of the article recommends avoiding the shell script wrappers, and executing java directly, with the appropriate environment and command line.
I have arch linux failing on a device. The device doesn’t have any screen, it doesn’t respond to network. So I take its SD card, insert it in ubuntu desktop, see a fresh system.journal there and… How to see what is inside?
The system has very old boots (2 and 3 years old), which are not recycled and I haven’t been able to vacuum them:
I wonder if systemd-journald is a new implementation of syslog protocol, or rather, it uses syslog implementations, such as rsyslog, syslog-ng
I’m experiencing a very weird issue with a fresh Fedora 21 image on a Linode instance. I cannot reproduce it outside of Linode. The issue is that my systemd journal is not persistent across reboots. According to the documentation: