| 1 |
On Thursday 15 December 2005 20:06, Brian Harring wrote: |
| 2 |
> On Thu, Dec 01, 2005 at 07:41:22PM -0600, Brian Harring wrote: |
| 3 |
> <snip comments on parent emerge not killing child emerge> |
| 4 |
> |
| 5 |
> > Either way, here's the issue, atexit registers work fine across forks, |
| 6 |
> > portage.portagexit is registered prior to portage_exec.cleanup, so the |
| 7 |
> > main portage pid sits there and waits for the kids to go away on their |
| 8 |
> > own, then portage_exec.cleanup tries waxing the pids. |
| 9 |
|
| 10 |
Ok.. After a few reads, I finally figured out what you're saying here. |
| 11 |
|
| 12 |
> This is the only blocker for merging parallel-fetch as far as I can |
| 13 |
> tell- so... my vote is nuking the wait out of portage.portageexit |
| 14 |
> (it's exec subsystem crap, belong in exec's atexit (where it exists)). |
| 15 |
> Assuming no complaints there, issues with parallel-fetch going into |
| 16 |
> svn? |
| 17 |
|
| 18 |
Nuking the wait is fine if things will still work the same.. I'm kind of |
| 19 |
wondering if ctrl-c'ing behaviour will change - how gets the ctrl-c first? |
| 20 |
|
| 21 |
-- |
| 22 |
Jason Stubbs |
| 23 |
-- |
| 24 |
gentoo-portage-dev@g.o mailing list |
Archives