Perl flock - f_rdlck not working

1) I execute the first program with the following statements:

$UNLOCK = 8;

unless (open(INFILE, "test.tmp"))
      print $query->header;
      &message("Unable to open in file");
flock (INFILE, $UNLOCK);

3) I execute a second pgm immediately after the first. The second pgm tries to read the same file(i.e. INFILE):

The second file successfully reads the INFILE before the first program completes; in other words, the $READLOCK in the first pgm is not locking file INFILE. By the way, the $EXCLUSIVE works correctly!!

Platform: UNIX - Solaris

object: $READLOCK must prevent any other file(i.e. read lock) from reading it. One solution is to execute chmod in the first pgm and set INFILE to 333. After it is complete, change it back to 644. However, I do not like this hack!!
Who is Participating?
yes thats right.
i think its working properly as its supposed to. Lock 1 is a shared lock, so other processes can still read from the locked file.

here is some PERL documentation that talks about file locks.


   Establishes a shared lock on the file (read lock).


   Establishes an exclusive lock on the file (write lock).

Also the polite process customarily indicates its intent to read from the file by requesting a LOCK_SH. Many processes can have
simultaneous shared locks on the file because they (presumably) won't be changing the data. If a process intends to write to the
file, it should request an exclusive lock via LOCK_EX
ronandersenAuthor Commented:

I am questioning the lock_sh. Why would you want to allow other people to read a file if a pgm request a read lock??

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

lock sh is a shared lock i.e. the file can be read from. Thats the actual implementation of a shared lock.

if you dont what to allow any other process to read from the file you would need an exclusive lock (as you have yourself mentioned above).
1 is a shared lock.  If you don't want to share, use an exclusive lock.
Also, flock does not lock out other programs doing a read or a write, flock locks out other programs doing a flock.
ronandersenAuthor Commented:

We are getting closer..

I tried using the exclusive lock on the first pgm, however, the second pgm still was able to read the file..

How would I prevent another process from reading a file??
The other process should not read unless it has aquires a flock.
ronandersenAuthor Commented:
For those of you responding,

When I flock a file as exclusive, other files can still read the locked file. Is this correct??
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.