X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <21e1598b0710081437m3f43ae06k9b2f58ec41819be6@mail.gmail.com>
Date: Mon, 8 Oct 2007 23:37:16 +0200
From: "Damjan Lango" <damjan DOT lango AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: file locking behaviour
In-Reply-To: <21e1598b0710081432g3cedf377wbb69d023cf08bb22@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <21e1598b0710081432g3cedf377wbb69d023cf08bb22 AT mail DOT gmail DOT com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Hello!

I have a program that uses:

lock.l_type = F_WRLCK;
fcntl(log->handle, F_SETLK, &lock)

the file is then locked also for reads, is that correct behaviour?
I thought that only writing would be locked.
on unix the file stays readable even if using the above code.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/