https://bz.apache.org/bugzilla/show_bug.cgi?id=64452
--- Comment #13 from Yann Ylavic <ylavic....@gmail.com> --- (In reply to Ruediger Pluem from comment #11) > Why should a failing cleanup kill the cleanup chain? If the cleanups are run > by apr_pool_clear or apr_pool_destroy no return code is checked and the > cleanup functions in the chain are all executed regardless of their return > value. Yeah, I don't know why I thought that.. I can't see any reason for that file stay then, it should be cleaned up with the request (i.e. always), and there seems to be no child crash. (In reply to Bernhard Friedreich from comment #0) > > Using systemd with PrivateTmp enabled the files are cleaned up on restart of > the unit. If using "legacy" sysv init Scripts we need to stop httpd, clean > up /tmp and start up again as httpd still holds a file handle open to every > modproxy.tmp.* file. Is there something special on your system that prevent opened file to be removed? It shouldn't be an issue on unix systems usually. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
