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
On Mo, 14.08.17 22:31, Sergei Franco (sergei.fra...@gmail.com) wrote:
> 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
>
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
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).
7
> *To:* Zhujiafa <zhuji...@huawei.com>
> *CC:* Reindl Harald <h.rei...@thelounge.net>; systemd-devel@lists.
> freedesktop.org
> *Subject:* Re: [systemd-devel] Outputting STDOUT and STDERR to current
> $SSH_TTY
>
> This is not recommended. Forwarding is currently implemented
&
From: vcap...@pengaru.com<mailto:vcap...@pengaru.com>
Date: 2017-08-12 02:57
To: Zhujiafa<mailto:zhuji...@huawei.com>
CC: Reindl Harald<mailto:h.rei...@thelounge.net>;
systemd-devel@lists.freedesktop.org<mailto:systemd-devel@lists.freedesktop.org>
Subject: Re: [systemd-devel
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
>
Doing that directly makes little sense. The terminal will eventually go
away, and your service will start getting write errors for stdout.
Instead it would be better if systemctl could spawn `journalctl --follow
--unit=`... I remember it used to have a follow option for status.
On Fri, Aug 11,
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 start
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
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
11 matches
Mail list logo
