From owner-freebsd-stable@FreeBSD.ORG Sun Jul 3 15:42:37 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED4ED16A41C for ; Sun, 3 Jul 2005 15:42:37 +0000 (GMT) (envelope-from andrea@acampi.inet.it) Received: from acampi.inet.it (acampi.inet.it [213.92.1.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1C9943D45 for ; Sun, 3 Jul 2005 15:42:37 +0000 (GMT) (envelope-from andrea@acampi.inet.it) Received: by acampi.inet.it (Postfix, from userid 1000) id C1AA44D; Sun, 3 Jul 2005 17:42:35 +0200 (CEST) Date: Sun, 3 Jul 2005 17:42:35 +0200 From: Andrea Campi To: Niki Denev Message-ID: <20050703154235.GB64535@webcom.it> References: <200506291704.50185.ndenev@icdsoft.com> <20050630174315.C66660@mail.prgmr.com> <42C71914.9090503@cytexbg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42C71914.9090503@cytexbg.com> User-Agent: Mutt/1.5.9i Cc: Luke Crawford , freebsd-stable@freebsd.org Subject: Re: background fsck can be dangerous! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jul 2005 15:42:38 -0000 On Sun, Jul 03, 2005 at 01:45:40AM +0300, Niki Denev wrote: > Before the background fsck finished some files were unreadable, > and they happened to be some libraries used by my mail software. > After the fsck finished these libraries were accessible again and > everything was normal and working, at least this is what it looked > like to me. > So, i think that if i had disabled background fsck (as i did now) > i should have skipped the loss of these about ten emails... IMHO this is something you need to solve no matter what. Failure of a local delivery program shouldn't cause lost or bounced emails; fixing this is usually just a matter of wrapping the program in appropriate shell magic to return the "temporary failure" error level (75 I think). For instance, when using postfix you can just use the following: mailbox_command = /your/local/script || exit 75 This way, even if the script fails running for *any* reason, postfix will just requeue your email. Again, this is not postfix-specific at all. Bye, Andrea -- Press every key to continue.