From tomcat-dev-return-46676-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org Fri Jul 02 15:26:13 2004 Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 34062 invoked from network); 2 Jul 2004 15:26:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Jul 2004 15:26:13 -0000 Received: (qmail 86797 invoked by uid 500); 2 Jul 2004 15:26:04 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 86660 invoked by uid 500); 2 Jul 2004 15:26:02 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 86619 invoked by uid 99); 2 Jul 2004 15:26:01 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [208.48.139.185] (HELO forty.greenhydrant.com) (208.48.139.185) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 02 Jul 2004 08:25:58 -0700 Received: from [10.0.0.10] (66-75-244-1.san.rr.com [66.75.244.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by forty.greenhydrant.com (Postfix) with ESMTP id 8BCF6E3912 for ; Fri, 2 Jul 2004 08:25:44 -0700 (PDT) Message-ID: <40E57E76.2050508@greenhydrant.com> Date: Fri, 02 Jul 2004 08:25:42 -0700 From: David Rees User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: [5.next] Progress References: <40B9EDC6.3070002@apache.org> <40C9E2EC.1000206@apache.org> <40D89680.2090904@apache.org> <40D9C59C.9020501@apache.org> <00bc01c45951$3df8e000$3d37a8c0@bbarkerxp> <40D9D440.2080409@apache.org> <40E0B1CE.6010801@apache.org> <40E2FD94.3000304@apache.org> <40E4CC89.2000601@apache.org> <40E52742.9050805@apache.org> In-Reply-To: <40E52742.9050805@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Remy Maucherat wrote, On 7/2/2004 2:13 AM: > Jeanfrancois Arcand wrote: >> Remy Maucherat wrote: >>> Speaking of which, does anyone know any OSes (besides Windows) which >>> lock files ? >> >> NFS sometimes lock file (I did see a similar problem with Solaris) > > Thanks for the tip. I'll code in Windows by default, and add a flag to > enable/disable then, since I don't think there's a way to determine if > something is coming from NFS. Although you can lock files over NFS on Unix systems, it should behave no differently than if you were to lock the file on any other filesystem. In other words, unless you explicitly lock the file and check that the file is locked (as locks are only advisory on Unix, they don't stop you from performing any operations if you really want to) you should not have any of the same file locking issues on Unix that you do on Windows. See the the flock and fcntl man pages for more information on Unix file locking. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org