| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
in single atomic non-blocking read() calls, similar to how
AbstractPollTask._read_buf() does it. If the read fails, exit with
status 2 so that best_version() and has_version() can detect the
error and die when necessary.
|
|
|
|
| |
doesn't need any of that stuff.
|
| |
|
|
|
|
| |
signal.alarm().
|
|
|
|
| |
handle interaction with the signal module.
|
|
|
|
|
| |
orphan is left for any reason then it will exit with an error message
instead of hanging indefinitely.
|
|
|
|
|
| |
atomc reading and writing of whole pickles. This should be the least
error-prone approach, given the non-blocking nature of the streams.
|
| |
|
| |
|
| |
|
|
|
|
| |
replacement for EBUILD_EXIT_STATUS_FILE.
|
|
|
|
| |
stdout could corrupt the intended output of this program.
|
|
processes can to communicate with portage's main python process.
Here are a few possible uses:
1) Robust subshell/subprocess die support. This allows the ebuild
environment to reliably die without having to rely on signal IPC.
2) Delegation of portageq calls to the main python process, eliminating
performance and userpriv permission issues.
3) Reliable ebuild termination in cases when the ebuild has accidentally
left orphan processes running in the backgraound (as in bug 278895).
|