This is not recommended. Forwarding is currently implemented synchronously in journald, and can have a very substantial negative impact on journald performance in general as a result.
BTW: are we not averse to top-posting on systemd-devel? Regards, Vito Caputo On Fri, Aug 11, 2017 at 05:47:15AM +0000, Zhujiafa wrote: > add > " systemd.journald.forward_to_console=1 " > to your kernel parameters. > > > ________________________________ > ======================== > ZhuJiafa > email: zhuji...@huawei.com<mailto:zhuji...@huawei.com> > tel: +86 18651652661 > > From: Reindl Harald<mailto:h.rei...@thelounge.net> > Date: 2017-08-11 13:37 > To: > systemd-devel@lists.freedesktop.org<mailto:systemd-devel@lists.freedesktop.org> > Subject: Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY > > > > Am 11.08.2017 um 04:29 schrieb Sergei Franco: > > I am trying to retain behaviour of the startup scripts the same as sysvinit. > > For example, on sysv the script outputs feedback to the console when the > > stopping and starting is done via console. > > With systemd all output is "hidden", and to see the output you need to > > check the journal (or syslog if configured). There is no feedback. > > > > Is it possible to configure StandardOutput=tty (and StandardErrror) > > where TTYPath= is set to current $SSH_TTY env (be that > > /devpts/0,/dev/pts/1 or /dev/pts/n)? > > no, because PID1 is a completly different process than any TTY > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > _______________________________________________ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel