Am 23.01.20 um 19:32 schrieb Mantas Mikulėnas: > On Thu, Jan 23, 2020 at 7:36 PM Reindl Harald <h.reindl@xxxxxxxxxxxxx > <mailto:h.reindl@xxxxxxxxxxxxx>> wrote: > > > > Am 23.01.20 um 18:32 schrieb Roger Pack: > > Forgive me if this is too naive, but would it be possible for > > systemctl to "immediately start outputting logs" (journalctl type > > output) while it is in the middle of running a command? Ex: while > > running "systemctl stop my_server" it could show the logs so we could > > see what is going on? I do miss that from the /etc/init.d days and > > feel so blind with systemctl now. > > Thoughts? > > and why don't you jsut write a shell alias or simple wrapper for such > trivial tasks? > > frankly "systemctl restart" hast to shut up because otherwise it would > trigger cron mails and when you have to write a special option anyways > you can also wirte an alias and be done > > > I don't think cron jobs are very high on systemctl's priority list. > Certainly lower than interactive use by the sysadmin. And if you > actually have to write a cron job, you can just add --quiet and be done? irrelevant - that's only one example "I do miss that from the /etc/init.d days and feel so blind with systemctl now" - where did classical initscripts show service logs at stop? systemctl does with "systemctl status" including stdout/stderr the point is that it has to be quiet unless there is something going wrong - imagine your webserver logs to journald and spits out millions of lines at restart _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel