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 terminal systemctl was called - the rest is done by crond as all the years beforeThis isn't how systemd works -- systemctl does *not* run any jobs by itself, it just asks pid 1 [1] to run a job. Thus the stdout/err of systemctl are completely irrelevant here.
since "systemctl start" on the shell waits until the "oneshot" service is finished it can't be impossible that pid 1 geives back the tasks output
To do what you want to do, don't put the code that you want to run into a systemd unit, just run it straight away. Then you don't have the indirection, and whatever you run will just output straight to stdout/err
in the first mail i wrote: "migrate cronjobs to systemd-units for using ReadOnlyDirectory and other security otpions"
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
