[systemd-devel] Fwd: Handling ExecStop failure

[Lennart Poettering]

On Mon, 23.05.16 10:56, Reindl Harald (h.reindl at thelounge.net) wrote:

> in a shell it works fine

Hmm, that's strange...

> but i talk about cronjobs like "8,38 * * * * root
> /usr/local/bin/spamfilter-fetch-samples" where the shell-script invokes
> systemd-run which finally calls a php-script producing output if there where
> sammples on the imap-folders not already classified with BAYES_99
> 
> the intention is to use systemd-capabilities like "-p
> ProtectSystem=full,ProtectHome=yes" starting with F24 and behave like a
> classical cronjob -> producing emails to all administrators
> 
> >This didn't always works though, and it was pretty nasty to get right
> >actually. The core of the problem is really that "-t" actually
> >allocates a tty, and ttys know no clean concept of single-direction
> >EOF, but only bi-directional hangups. Thus, using ttys as the backend
> >for inner components of shell pipeliness, without losing trailing data
> >is really hard to get right.
> >
> >But anyway, this should work now
> 
> at least not on current Fedora releases, maybe it works now

OK. In case you can reproduce this with a current systemd version one
day, then please file an issue, and please try to keep the testcase
minimal...

Lennart

-- 
Lennart Poettering, Red Hat