comment on

Everyone explained very well what happens with signals and END blocks. Now that that's cleared up...

If the record file is not accessed or seen by any other process, you can unlink it after it's been openned, and the file handle will stay valid. The kernel will clean up the disk space it uses when the last file descriptor open on it is closed, which will happen whether you close it explicitly, die a clean death, or get shot down by some violent signal.

-nuffin
zz zZ Z Z #!perl

In reply to Re: Signals and END block by nothingmuch
in thread Signals and END block by Marcello

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks