This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Re: file locking (F_GETLK) porting workaround anyone???


At 09.07.01 10:28, you wrote:
>On Mon, Jul 09, 2001 at 09:56:20AM +0200, hardon wrote:
>> Any known workaround for the unimplemented F_GETLK, file locking func???
>> Whats the big deal with this thing anyway??
>> If we don't need the lockers pid, just try std. lock and check for errors, 
>> right??
>
>You're welcome to contribute F_GETLK and F_SETLK(W) in Cygwin if you've
>found a way to implement them correctly.

What's wrong with F_SETLK(W)? Missing signal interrupt support? 
If so, could consistent asynchronous file IO (on NT) fix this?
LockFileEx do support asynchronous IO.

Proper implementation of F_GETLK could be done (on NT) with use of a kernel mode filesystem filter driver.


>Corinna
>
>-- 
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Developer                                mailto:cygwin@cygwin.com
>Red Hat, Inc.
>
>--
>Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting:         http://cygwin.com/bugs.html
>Documentation:         http://cygwin.com/docs.html
>FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]