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 before
This 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. 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. Martin [1] Or the user's systemd instance, but in this context it's really the same thing -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
