> There is one caveat, however. If a process that has the lock crashes without
> releasing the lock, the lock file will stay around and prevent other
> processes to acquire it. Then you will have to manually remove it. I
> generally prefer a solution where the pid of the locking process is writt
Jason Friedman writes:
> The lockfile solution seems to be working, thank you.
There is one caveat, however. If a process that has the lock crashes without
releasing the lock, the lock file will stay around and prevent other processes
to acquire it. Then you will have to manually remove it. I
The lockfile solution seems to be working, thank you.
On Fri, Oct 11, 2013 at 10:15 PM, Piet van Oostrum wrote:
> Jason Friedman writes:
>
>> I have a 3rd-party process that runs for about a minute and supports
>> only a single execution at a time.
>>
>> $ deploy
>>
>> If I want to launch a seco
Jason Friedman writes:
> I have a 3rd-party process that runs for about a minute and supports
> only a single execution at a time.
>
> $ deploy
>
> If I want to launch a second process I have to wait until the first
> finishes. Having two users wanting to run at the same time might
> happen a fe
I have a 3rd-party process that runs for about a minute and supports
only a single execution at a time.
$ deploy
If I want to launch a second process I have to wait until the first
finishes. Having two users wanting to run at the same time might
happen a few times a day. But, these users will n
