Return-Path: X-Original-To: apmail-curator-user-archive@minotaur.apache.org Delivered-To: apmail-curator-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B668D10C03 for ; Fri, 30 Aug 2013 19:28:26 +0000 (UTC) Received: (qmail 55059 invoked by uid 500); 30 Aug 2013 19:28:26 -0000 Delivered-To: apmail-curator-user-archive@curator.apache.org Received: (qmail 54975 invoked by uid 500); 30 Aug 2013 19:28:24 -0000 Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@curator.incubator.apache.org Delivered-To: mailing list user@curator.incubator.apache.org Received: (qmail 54957 invoked by uid 99); 30 Aug 2013 19:28:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 19:28:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pacesysjosh@gmail.com designates 209.85.128.170 as permitted sender) Received: from [209.85.128.170] (HELO mail-ve0-f170.google.com) (209.85.128.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Aug 2013 19:28:16 +0000 Received: by mail-ve0-f170.google.com with SMTP id 15so1693878vea.29 for ; Fri, 30 Aug 2013 12:27:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=4HtjLXUSMWGnylBy+tVrOpppgruRo4BzD+Ko5e2611w=; b=EMZSdEV/xPnnWox/FAJZPidxfUFCZx9u/+/oieeWEGA9czyw6vAkGM5chWcHpmh7/V 003wABEcsOOVbEgWxXsB8H6e9+3IRZCObc/MQid03FqlwEHtJDJNkN9X7U8PnUfHVEpT kciSe2w/nwPtfnJ5NmyOx0/9XaBiLsaSj13PjttP/Tb6dQkru2YuBExbzHBrBzr74Oam cLS2G2Vd2NltAYvPXrq9HsWJhZfAXt9KumLGRpl6xPn3ZvvtYuuM+pm0kelNM4SPr83X UtZmKiC2/c1+LLOe1SMvYRMNB3HdMuHxEuS0EuXTBZ8jQmoxZopWLFtc4xy3C37Z0Nmq EhJQ== MIME-Version: 1.0 X-Received: by 10.58.235.69 with SMTP id uk5mr9721883vec.17.1377890875654; Fri, 30 Aug 2013 12:27:55 -0700 (PDT) Received: by 10.220.111.212 with HTTP; Fri, 30 Aug 2013 12:27:55 -0700 (PDT) Date: Fri, 30 Aug 2013 12:27:55 -0700 Message-ID: Subject: Shared lock usage From: Josh Stone To: user@curator.incubator.apache.org Content-Type: multipart/alternative; boundary=047d7bd6c2c42ec8ba04e52f38d0 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6c2c42ec8ba04e52f38d0 Content-Type: text/plain; charset=ISO-8859-1 I'm using shared locks and just wanted to learn what's the best way to clean them up when I'm done. When is the appropriate time to delete the node that I use for my lock? Can I delete it right after releasing it? Would this possibly cause problems with another process that might be waiting on that lock or attempting to concurrently create/acquire a lock on that path? Thanks, Josh --047d7bd6c2c42ec8ba04e52f38d0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I'm using shared locks and just wanted to learn what's the best w= ay to clean them up when I'm done. When is the appropriate time to dele= te the node that I use for my lock? Can I delete it right after releasing i= t? Would this possibly cause problems with another process that might be wa= iting on that lock or attempting to concurrently create/acquire a lock on t= hat path?

Thanks= ,

Josh

--047d7bd6c2c42ec8ba04e52f38d0--