В Thu, 9 May 2013 18:33:51 +0200
John Connor
Two comments (hopefully constructive): It would be useful for debugging if systemctl had an option to show output on the screen, rather than dumping it in a journal which you then have to search through. This should be a command-line option, because you would normally use it only for debugging, not for a normal boot. Secondly, the man page for systemd-journalctl mentions that you can filter journal contents using FIELD=value, but (except for one example) it doesn't indicate where the field identifiers are defined. It would make the journal a lot more usable if it was clear where to find this information.
You should raise these issues upstream. They are valid, and while extending documentation is easy, I'm not sure getting output of service redirected to your terminal is really possible. But someone may suggest other technique to facilitate debugging.
For example, when you run some scripts (such as /etc/init.d/tomcat) from the command line, you get a message that they are being "redirected", and systemd runs some other script (in this case tomcat-sysd). This happens even if you rename the corresponding service file to something else. So what sets up this redirection, and how would I prevent it if for some reason (such as debugging) I wanted to?
SYSTEMD_NO_WRAP=yes /etc/init.d/foo ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org