Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 51731 invoked from network); 15 Jun 2006 16:58:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Jun 2006 16:58:40 -0000 Received: (qmail 34761 invoked by uid 500); 15 Jun 2006 16:58:39 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 34724 invoked by uid 500); 15 Jun 2006 16:58:39 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 34715 invoked by uid 99); 15 Jun 2006 16:58:39 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 09:58:39 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.141] (HELO e1.ny.us.ibm.com) (32.97.182.141) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2006 09:58:35 -0700 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e1.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5FGwDhB009175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 15 Jun 2006 12:58:13 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k5FGwDvX234846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 15 Jun 2006 12:58:13 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k5FGwDqu014263 for ; Thu, 15 Jun 2006 12:58:13 -0400 Received: from [127.0.0.1] (IBM-IKEJ04B1IMA.usca.ibm.com [9.72.133.43]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5FGwAfa013987 for ; Thu, 15 Jun 2006 12:58:13 -0400 Message-ID: <449191A0.6020507@sbcglobal.net> Date: Thu, 15 Jun 2006 09:58:08 -0700 From: Mike Matrigali Reply-To: mikem_app@sbcglobal.net User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: [Enhancement] Name the ' db.lck' file within a booted db to be '.db.lck' References: <44908734.5080007@gmail.com> In-Reply-To: <44908734.5080007@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Note that this change is not as easy as it seems. I believe there are all sorts of upgrade issues. I don't think it is possible to change the name in 10.1 as 2 different versions of CS running in different jvms won't agree on the object they are locking. I guess for a hard upgrade one could lock both files, and for db's booted that have already been upgraded to 10.2 one should be able to lock the new name. Does anyone know if java guarantees that files starting with "." is a valid filename on all the platforms. We have in the past tried to be very safe in our filename choices - mostly trying for 8.3 standard. Rajesh Kartha wrote: > Hi, > > I was wondering, if we could name the 'db.lck' file within a Derby > database to be '.db.lck' to indicate the db has been booted. > > By appending a '.' before the file name most of the OSes will consider > it as a hidden file and will not show > in the default directory listing unless an 'ls -a' is used. This can > avoid unwanted/accidental deletion of this file on Linux/Unix. > > I will open a JIRA enhancement request to track this. > > Regards, > Rajesh > > > > > > >