Message239375
eryksun, thank you for the explanation, the penny finally dropped for me. It's the *other* child processes that keep the file open, not the parent. Actually this bug started hitting me after I *stopped* doing exactly what you suggest (fdopen on the temp file), and instead started using file names generated by my program (opened with regular "open") and now I see why that is. If I use os.fdopen with the O_NOINHERIT flag, it works as expected. |
|
Date |
User |
Action |
Args |
2015-03-27 06:01:42 | Emil.Styrke | set | recipients:
+ Emil.Styrke, terry.reedy, amaury.forgeotdarc, ggenellina, eckhardt, javen72, brian.curtin, eryksun |
2015-03-27 06:01:42 | Emil.Styrke | set | messageid: <1427436102.08.0.942340919528.issue4944@psf.upfronthosting.co.za> |
2015-03-27 06:01:42 | Emil.Styrke | link | issue4944 messages |
2015-03-27 06:01:41 | Emil.Styrke | create | |
|