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

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

[systemd-devel] type=notify not working as intended

Hello all, I have scripted a service unit as follow. [Unit] Description="A test service" After=epmd.service epmd.socket [Service] ExecStart=/home/otpuser/bin/start Type=notify NotifyAccess=all WorkingDirectory=~ User=otpuser Group=otp Restart=always RestartSec=3 [Install]

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

Admins expect output when starting and stopping services. This is even more important when there are runbooks and other processes involved. The journalctl output is very messy (because it is a log). When you are on call and you have to deal with an issue at 3am in the morning, the messy output

[systemd-devel] systemd-logind fails to start

I have an old arm5 plug computer that is running latest arch linux arm. # uname -a Linux delilah 4.4.77-1-ARCH #1 PREEMPT Tue Jul 18 02:17:24 UTC 2017 armv5tel GNU/Linux # systemctl --version systemd 234 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT

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

" With systemd all output is "hidden", " He just wanted to see more detailed boot messages too determine the .service is correct ! ZhuJiafa email: zhuji...@huawei.com tel: +86 18651652661 From:

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

Am 14.08.2017 um 12:31 schrieb Sergei Franco: Admins expect output when starting and stopping services admins should learn to deal with their system This is even more important when there are runbooks and other processes involved. The journalctl output is very messy (because it is a log).