On Fri, Jan 2, 2015 at 10:51 AM, Bradley Asztalos <b...@customweather.com> wrote:
> Taking this one step further, I know of course there are other ways to do > this, but what about a way to have sem die if it cannot immediately acquire > execute? Something like --die_young so that it could be used not only to > serialize but to disallow a run if there is already a process running with > the same lock_id. So that is almost the opposite of --semaphoretimeout Maybe it should be able to take a negative value: If you cannot get the semaphore within 2 seconds, give up. sem --semaphoretimeout -2 do_stuff /Ole