Re: [systemd-devel] "StandardOutput=console" don't work as expected

Hi, On Wed, Dec 30, 2015 at 2:52 AM, Michael Chapman wrote: > On Wed, 30 Dec 2015, Reindl Harald wrote: >>> > i am asking for StandardOutput=console get piped to the terminal >>> > systemctl was called - the rest is done by crond as all the years >>> > before >>> >>>

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Reindl Harald [2015-12-30 11:10 +0100]: > i just want systemd *not to touch* the stdout behavior when asked to do so - > it don't need to know anything about ssh ptys, just don't touch stdout > > i am asking for StandardOutput=console get piped to the terminal systemctl > was called - the rest is

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Reindl Harald wrote: Standard mailing list etiquette is to reply-to-all on which mailing-list is that the case? be assured it's NOT standard on the majority on most it is considered rude OK. I'm not going to argue the matter. > i am asking for StandardOutput=console

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Reindl Harald [2015-12-30 11:35 +0100]: > in the first mail i wrote: "migrate cronjobs to systemd-units for using > ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This should give you both, direct stdout/err and the

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 12:09 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:35 +0100]: in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Martin Pitt wrote: Reindl Harald [2015-12-30 11:35 +0100]: in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions" OK, I suggest to use systemd-run -t then, like Michael Chapman already suggested. This should

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:25 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, 30 Dec 2015, Reindl Harald wrote: Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs which need to output stuff to ssh ptys?

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:52 schrieb Michael Chapman: On Wed, 30 Dec 2015, Reindl Harald wrote: Standard mailing list etiquette is to reply-to-all on which mailing-list is that the case? be assured it's NOT standard on the majority on most it is considered rude OK. I'm not going to argue the

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald wrote: > fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo > and the PID instead just the output) but that don't help much in a > SSH-Session.. > > > Am 30.12.2015 um 01:26 schrieb Reindl Harald:

Re: [systemd-devel] "StandardOutput=console" don't work as expected

On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald wrote: > > > Am 30.12.2015 um 10:37 schrieb Mantas Mikulėnas: > >> On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald > > wrote: >> >> fine, on a real TTY (CTRL+ALT+F2)

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 11:24 schrieb Martin Pitt: Reindl Harald [2015-12-30 11:10 +0100]: i just want systemd *not to touch* the stdout behavior when asked to do so - it don't need to know anything about ssh ptys, just don't touch stdout i am asking for StandardOutput=console get piped to the

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:37 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 2:40 AM, Reindl Harald > wrote: fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo and the PID instead just the output) but that don't

Re: [systemd-devel] "StandardOutput=console" don't work as expected

Am 30.12.2015 um 10:50 schrieb Mantas Mikulėnas: On Wed, Dec 30, 2015 at 11:46 AM, Reindl Harald > wrote: Do you really have cronjobs which need to output stuff to ssh ptys? i have hundrets cronjobs which are running silent

[systemd-devel] "StandardOutput=console" don't work as expected

why is there only logging instead "TEST" written to the terminal starting a oneshot-service or in case it's a entry in /etc/crontab triggering a cronmail becaus the output? that's not helpful when try to migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions

Re: [systemd-devel] "StandardOutput=console" don't work as expected

fine, on a real TTY (CTRL+ALT+F2) the echo appears (cluttered with echo and the PID instead just the output) but that don't help much in a SSH-Session.. Am 30.12.2015 um 01:26 schrieb Reindl Harald: why is there only logging instead "TEST" written to the terminal starting a

Re: [systemd-devel] "StandardOutput=console" don't work as expected

30.12.2015 03:40, Reindl Harald пишет: > fine, on a real TTY (CTRL+ALT+F2) the echo appears It is not echo, it is "+console" part of StandardOutput - i.e. it is still logging, not output. > (cluttered with echo > and the PID instead just the output) but that don't help much in a >