From owner-cvs-all Mon Dec 11 7:12:34 2000 From owner-cvs-all@FreeBSD.ORG Mon Dec 11 07:12:30 2000 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B23A637B400; Mon, 11 Dec 2000 07:12:29 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id eBBFCTe42004; Mon, 11 Dec 2000 10:12:29 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 11 Dec 2000 10:12:28 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David O'Brien" Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc crontab In-Reply-To: <20001210234818.A73780@ehlo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: robert@fledge.watson.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (dropping James FitzGibbon from the destination list since my mailer is complaining it can't resolve MX records for ehlo.com right now) It also strikes me that maybe to deal with the collision problem, you should be using seperate lock files for each event. I.e., I personally don't care if daily and weekly run at the same time, but if daily and the next daily run at the same time, I do care. So the locking domain should reflect that: /var/run/periodic/daily.lock /var/run/periodic/weekly.lock Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message