Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-10 Thread Zhujiafa
add " systemd.journald.forward_to_console=1 " to your kernel parameters. ZhuJiafa email: zhuji...@huawei.com tel: +86 18651652661 From: Reindl Harald Date: 2017-08-11 13:37 To:

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-10 Thread Reindl Harald
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

[systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-10 Thread Sergei Franco
Hi, 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

Re: [systemd-devel] Clarification on unit state meanings

2017-08-10 Thread Lennart Poettering
On Mi, 09.08.17 20:10, James Forcier (james.forc...@coreos.com) wrote: > Hey all, > > I noticed some odd ways `systemctl status` reports the status of units when > they're enabled via symlinks in target.{wants,requires} directories in /usr. > In > particular, units with Install sections enabled