Backport #3227
closedtempfile.rb seems to have a broken unlink function
Description
=begin
When using tempfile on Ruby 1.8, unlink does not close the underlying file, which is useful on POSIX systems to stop other processes from accessing the temporary files. Similar suggestion is available in the comments for Tempfile#unlink on Ruby 1.9's tempfile.rb but there, the file gets closed before being unlinked, and thus you cannot access it any more.
I'm not sure if the change in behaviour is wanted or not, but this at least seems to break Rack (from which I extracted the attached testcase). Either the suggestions should go, or it shouldn't close.
=end
Files
Updated by coatl (caleb clausen) over 14 years ago
=begin
I just want to be clear on what you mean; you're saying the Tempfile should still be usable (not closed) after Tempfile#unlink has been called, right?
Works for me using a 1.9.2dev build from 2010-04-24 (6 days ago). Maybe something needs to be backported to 1.9.1?
=end
Updated by mame (Yusuke Endoh) over 14 years ago
- Target version set to 1.9.1
=begin
Hi,
I think Caleb is right.
r24662 should be merged into ruby_1_9_1.
This ticket is moved to Backport tracker. Thanks.
--
Yusuke Endoh mame@tsg.ne.jp
=end
Updated by jeremyevans0 (Jeremy Evans) over 5 years ago
- Description updated (diff)
- Status changed from Open to Closed