Pathologically Eclectic Rubbish Lister | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
> In addition, I imagine that the flocked file is
In general, no, there is no reason to call flock, especially if you are about to close the file. Perl will unlock the file for you. If you exit the script without closing the file, perl will unlock it and close it for you. I can think of only two times where one might want to explicitly unlock a file through flock: First, you may want to check the return code and see whether or not the unlock succeeded or failed. In reality, this is a very rare event. File locking, on the other hand, can fail for many reasons, and the value should always be checked. Once a file has been locked, in other words, it is very unlikely that an unlock will fail. I would only add this in after a problem had been found, as part of an advanced debugging process. Then again, checking the status doesn't really make your code any slower, so whatever you are comfortable with. The second reason to unlock a file is if there is going to be a long pause in which you are not going to use the file, but you do not want to close it yet. For example, take this script that adds a timestamp to a logfile at a random interval (perhaps it picks a random visitor to win something?)
Not a very useful script, but it illustrates the point. I'd probably open and close it every time. In reply to RE: RE: Re: This is weird...
by turnstep
|
|