From owner-freebsd-questions Sat Jan 1 13:29:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 134F115121 for ; Sat, 1 Jan 2000 13:29:44 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id XAA11299 for ; Sat, 1 Jan 2000 23:29:40 +0200 Message-Id: <3.0.6.32.20000101232921.00abfcf0@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sat, 01 Jan 2000 23:29:21 +0200 To: freebsd-questions@freebsd.org From: Pekka Savola Subject: Huge crontab jobs are not run. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I noticed that *huge* crontab entries in /etc/crontab aren't run on my 3.4-STABLE (the same in 3.2-REL). E.g. ----- 1 0 * * 1 root /usr/local/sbin/logrotate ----- Will not be run. Logrotate does some really heavy httpd log checking and resolving - Like 1-2 hours job on a P3/500. Replacing /usr/local/sbin/logrotate with some neat little script seems to be run nicely. Also, 'touch /etc/crontab' doesn't help any. Running the script manually works fine. Is there something I'm missing here? Are there some kind of timeouts for crontab scripts? Any ideas? TIA, Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message