From owner-freebsd-bugs Thu Aug 10 3:50: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8BCC237B7FD for ; Thu, 10 Aug 2000 03:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id DAA92390; Thu, 10 Aug 2000 03:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 10 Aug 2000 03:50:04 -0700 (PDT) Message-Id: <200008101050.DAA92390@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Paul Herman Subject: Re: conf/20498: All FreeBSD systems trigger massive late-night activity at the same times Reply-To: Paul Herman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/20498; it has been noted by GNATS. From: Paul Herman To: brian@FreeBSD.ORG Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: conf/20498: All FreeBSD systems trigger massive late-night activity at the same times Date: Thu, 10 Aug 2000 12:42:55 +0200 (CEST) On Thu, 10 Aug 2000 brian@FreeBSD.ORG wrote: > I don't believe it's appropriate to do this in periodic.conf. It > should be done in the crontab file to remove the fact that a > reboot between 2:00 and the actual start time would abort the > daily run. Good point. This seems to be a general problem (not just for periodic) and crontab would have the same difficulty, or? Timestamp files (eewww) would theoreticaly be a solution, but doesn't appeal to me practicaly. Not that I am for this feature as part of FreeBSD anyway... (just someone who reads -bugs, I'll crawl back into -questions now :) -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message