Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site sdcrdcf.UUCP
Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!burdvax!sdcrdcf!davem
From: davem@sdcrdcf.UUCP (David Melman)
Newsgroups: net.unix-wizards
Subject: flock(2) on 4.2bsd
Message-ID: <2721@sdcrdcf.UUCP>
Date: Mon, 24-Mar-86 16:35:50 EST
Article-I.D.: sdcrdcf.2721
Posted: Mon Mar 24 16:35:50 1986
Date-Received: Wed, 26-Mar-86 03:38:57 EST
Reply-To: davem@sdcrdcf.UUCP (David Melman)
Organization: System Development Corporation R&D, Santa Monica
Lines: 18

I am using the LOCK_EX (exclusive lock) operation on a file.
The manual states that if a lock already exists, the call should
block until lock is available.  But in testing,
if the lock exits, flock returns with an error, EWOULDBLOCK.

It behaves as if I specified (LOCK_EX|LOCK_NB) for the operation,
the LOCK_NB being no blocking, but I have NOT!

Am I doing something wrong?

David  Melman
uucp: sdcrdcf!davem
Subject: mail

I removed the 'm' flag from our uucp mailer in our sendmail.cf file.
Now multiple addresses reach their destinations on burdvax.

David