delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
X-WebMail-UserID: | hardon AT online DOT no |
Date: | Mon, 9 Jul 2001 09:56:20 +0200 |
From: | hardon <hardon AT online DOT no> |
To: | cygwin AT cygwin DOT com |
X-EXP32-SerialNo: | 50000140 |
Subject: | file locking (F_GETLK) porting workaround anyone??? |
Message-ID: | <3B4961EE@epostleser.online.no> |
Mime-Version: | 1.0 |
X-Mailer: | InterChange (Hydra) SMTP v3.61.08 |
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?? Gunnar Dalsnes. -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |