On Di, 15.08.17 09:14, Sergei Franco (sergei.fra...@gmail.com) wrote: > Please accept my apologies for HTML email (using gmail client). > > For our organisation mid-2016 was the year of systemd, and exposure > has been minimal (only new builds), so I guess you had a head start. I > fully grasp the config file layout and overrides (I use them to deal > with things like LimitNOFILE and ExecStartPost). My comments were from > perspective of someone recently coming from init scripts. I still > thinks /lib/ is bad place for system config (should have been another > directory in /etc/systemd). > > In contrast I had no issues with upstart what so ever. > > In any way, since it is going down towards personal attacks, lets go > back to original problem: > > How does one convey the service output (stdout/stderr) to the console > from which user initiated systemctl? I guess consensus is that you > cannot. > > If so, is it possible to make systemctl to display status after a state > change? > Eg: running systemctl restart apache2 it fires off systemctl status > apache2 after?
Try "journalctl -u apache2 -f" to get a live view on the stuff apache2 does, and everything systemd does with it. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
