From owner-freebsd-questions Sun Apr 26 06:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA28343 for freebsd-questions-outgoing; Sun, 26 Apr 1998 06:13:03 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from bbs.mpcs.com (bbs.mpcs.com [204.215.226.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27633 for ; Sun, 26 Apr 1998 06:06:11 -0700 (PDT) (envelope-from hgoldste@bbs.mpcs.com) Received: (from hgoldste@localhost) by bbs.mpcs.com (8.8.8/8.8.8/MPCS spamzap) id JAA20223; Sun, 26 Apr 1998 09:06:09 -0400 Date: Sun, 26 Apr 1998 09:06:09 -0400 From: Howard Goldstein Message-Id: <199804261306.JAA20223@bbs.mpcs.com> To: freebsd-questions@FreeBSD.ORG Cc: street@iName.com, kpielorz@tdx.co.uk Subject: Re: Protecting Shell scripts from deadlocks... In-Reply-To: <87zph990m6.fsf@kstreet.interlog.com> Reply-To: hgoldste@bbs.mpcs.com Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG street@iName.com wrote: : : There's a little utility called lockfile which is distributed as part : of procmail that can help with this. It has timeouts and retries and : lock forcing options that are handy. shlock (in the INN distribution) may also be an option. It's less powerful than lockfile though, lacking timeouts and retries... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message