note
KM
Your examples on file locking to avoid race conditions all have race conditions themselves. Let's go over some of what you wrote:<P>
First, some people do say 'eff-lock' :) Most things looked ok until the <b>All about flock</b> section. The concepts of LOCK_* is somewhat explained, but these values are constants which should be retrieved from the system header file which defines them. You should not define them in the script or create subroutines to do this. On an aside, you showed:
<P>
sub LOCK_SH { 1 } ## shared lock <BR>
sub LOCK_EX { 2 } ## exclusive lock<BR>
sub LOCK_NB { 4 } ## non-blocking <BR>
sub LOCK_UN { 8 } ## unlock<BR>
If you want to define a constant, you should include the prototype () like:
<P>
sub LOCK_SH () { 1 } ## shared lock <BR>
etc...
<P>
That's one way to make a constant, but.. back to the show..
<P>
One of the best ways to get these values is with the Fcntl module like:<P>
use Fcntl qw(:flock);
<P>
This will import your systems constants for those values. The next example given contains a race condition. Actually, the way you are explaining to get around a race condition, is really also a race condition. Not to worry, many people make this mistake and think that a simple flock() will make everything watertight. One of the problems is that the system itself may not finish writing to the file when the actual lock is released (remember, locks are only advisory, a file isn't actually frozen in some way), and another process reads the file before the write is comeplete. This may be a rare occasion, however. Another problem can occur when another process updates the file between the time the file is opened, and the lock is obtained. This is ano
7058
7058