Re: [dev] lock (1) - a dead simple lock script

From: Calvin Morrison <mutantturkey_AT_gmail.com>
Date: Fri, 11 Apr 2014 10:07:13 -0400

guys,

I have added a 'try_mkdir' function because we need to check each time
the cause of the failure. I think we should fail out if we don't have
permissions to create the lock during the loop (like during the first
check), rather than it EEXISTS. What do you think?

Calvin

On 11 April 2014 09:52, Calvin Morrison <mutantturkey_AT_gmail.com> wrote:
> On 11 April 2014 07:39, Calvin Morrison <mutantturkey_AT_gmail.com> wrote:
>> I think you're
>>
>>
>> On Apr 11, 2014 4:33 AM, "Truls Becken" <truls.becken_AT_gmail.com> wrote:
>>>
>>> On 2014-04-08, at 17:48, Calvin Morrison wrote:
>>>
>>> > The script will either create the lock and exit, or ping the lock
>>> > every two seconds until the lock is gone (via rmdir).
>>>
>>> I'm confused. Surely you also need to lock after old lock goes away?
>>>
>>> -Truls
>>>
>>
>> I think you're right thought, shouldn't another lock be established? I think
>> the code I'll merge at some point today resolves that.
>>
>> Calvin
>
> Sorry, next time mar77i, check your damned line endings. This I
> couldn't see from github website, but I reverted the commit. I don't
> want trailing ^M's everywhere. I merged FRIGNs cleanup instead.
Received on Fri Apr 11 2014 - 16:07:13 CEST