[systemd-bugs] [Bug 87732] nspawn catches kill signal only when using jenkins

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87732

Wulf C. Krueger <philantrop at exherbo.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |REOPENED

--- Comment #7 from Wulf C. Krueger <philantrop at exherbo.org> ---
(In reply to Lennart Poettering from comment #6)
> Hmm, what is stdin/stdout/stderr connected to when this happens?

>From https://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build:

"Jenkins and the child process are connected by three pipes
(stdin/stdout/stderr.) This allows Jenkins to capture the output from the child
process. Since the child process may write a lot of data to the pipe and quit
immediately after that, Jenkins needs to make sure that it drained the pipes
before it considers the build to be over. Jenkins does this by waiting for
EOF."

> Currently, this needs to be a tty, since nspawn provides it as a tty
> internally, too.

This changed between 217 and 218 as pointed out in comment #1. So I'm not quite
sure why...

> that's actually more complex than it sounds, and
> probably also requires some changes in systemd itself, if it shall be
> bootable without /dev/console existing...

... as it *worked* just fine and broke only recently. :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150205/650c1c15/attachment.html>