Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Adjust EbuildIpcDaemon pickle read and write code in order to ensure | Zac Medico | 2010-09-02 | 1 | -1/+4 |
| | | | | | atomc reading and writing of whole pickles. This should be the least error-prone approach, given the non-blocking nature of the streams. | ||||
* | Split out an EbuildIpcDaemon class from FifoIpcDaemon. | Zac Medico | 2010-08-12 | 1 | -42/+1 |
| | |||||
* | Add some pieces of an IPC framework that will eventually allow ebuild | Zac Medico | 2010-08-12 | 1 | -0/+108 |
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). |