Re: [dev] lock (1) - where does it go?

From: Dimitris Papastamos <sin_AT_2f30.org>
Date: Tue, 12 Jan 2016 16:26:31 +0000

On Tue, Jan 12, 2016 at 11:24:09AM -0500, Calvin Morrison wrote:
> On 12 January 2016 at 10:27, Dimitris Papastamos <sin_AT_2f30.org> wrote:
> > On Tue, Jan 12, 2016 at 09:35:59AM -0500, Calvin Morrison wrote:
> >> sorry to revive an old topic -
> >>
> >> I'd like to have this in with other utils, because i find it useful in
> >> my day to day work. I do not care about the licensing, feel free to
> >> use whatever license is appropriate.MIT/X I think is what is used
> >> around here.
> >>
> >> Would someone be willing to commit this into u/sbase for me?
> >
> > There is already flock(1) in sbase if that's what you mean.
> >
>
> No sorry, flock is a different program that the wraps flock().
> Somewhat evil and not going to necessarily work on all use cases. This
> was discussed length in a previous thread. This program uses
> directories which are helpfully atomic, to 'lock' a program from
> running until it's removed.

Care to clarify the limitations of flock?
Received on Tue Jan 12 2016 - 17:26:31 CET