Received: (at submit) by bugs.debian.org; 29 Jun 2001 23:23:14 +0000 From erno@fabulous.u--3.com Fri Jun 29 18:23:14 2001 Return-path: Received: from fabulous.u--3.com [::ffff:212.50.142.250] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15G7bN-0000YW-00; Fri, 29 Jun 2001 18:23:05 -0500 Received: by fabulous.u--3.com (Postfix, from userid 1000) id F12D882AB; Sat, 30 Jun 2001 02:22:49 +0300 (EEST) From: Erno Kuusela To: Debian Bug Tracking System Subject: unstuck nfs mount should not cause several days worth of cron jobs at once X-Reportbug-Version: 1.17 X-Mailer: reportbug 1.17 Date: Sat, 30 Jun 2001 02:22:49 +0300 Message-Id: <20010629232249.F12D882AB@fabulous.u--3.com> Delivered-To: submit@bugs.debian.org Package: cron Version: 3.0pl1-69 Severity: wishlist hello, i am not quite sure if this is the correct package to file the bug on, or how one might fix this, but it would be nice if the debian cron system had some way to resist nfs braindamage. there was a nfs mount the server of which had gone and when i got around fixing things there were about 20 logrotates and misc. things running, and my box seemed generally unhappy about this. perhaps crond should use some locking so that many copies of the same cron job don't wind up running at the same time, or similar. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux fabulous 2.2.19pre3 #1 Fri Dec 22 04:06:11 EET 2000 i586 Locale: LANG=C, LC_CTYPE=fi_FI Versions of packages cron depends on: ii debianutils 1.15 Miscellaneous utilities specific t ii libc6 2.2.3-5 GNU C Library: Shared libraries an ii libpam0g 0.72-25 Pluggable Authentication Modules l