X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CD3FDD85C3 for ; Tue, 18 Oct 2005 02:50:59 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35395-05 for ; Tue, 18 Oct 2005 05:50:55 +0000 (GMT) Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by svr1.postgresql.org (Postfix) with ESMTP id EFD72D85E2 for ; Tue, 18 Oct 2005 02:50:55 -0300 (ADT) Received: from lfix.demon.co.uk ([80.177.205.209] helo=cerberus.lfix.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 4.42) id 1ERkNC-000DKQ-7K; Tue, 18 Oct 2005 05:50:54 +0000 Received: from linda.lfix.co.uk ([192.168.1.1]) by cerberus.lfix.co.uk with esmtp (Exim 4.50) id 1ERkN3-0001Xt-R2; Tue, 18 Oct 2005 06:50:45 +0100 Subject: Re: postmaster blues after system restart From: Oliver Elphick Reply-To: olly@lfix.co.uk To: Tom Lane Cc: "Thomas F. O'Connell" , pgsql-admin@postgresql.org, Scott Marlowe In-Reply-To: <26905.1129613371@sss.pgh.pa.us> References: <39013461-BAB8-42A1-B2C9-E03CEC6B1C12@sitening.com> <26905.1129613371@sss.pgh.pa.us> Content-Type: text/plain Organization: LFIX Limited Date: Tue, 18 Oct 2005 06:50:49 +0100 Message-Id: <1129614649.8878.55.camel@linda.lfix.co.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit X-LFIX-MailScanner: Found to be clean X-LFIX-MailScanner-SpamCheck: not spam, SpamAssassin (score=-5.899, required 5, autolearn=not spam, ALL_TRUSTED -3.30, BAYES_00 -2.60) X-LFIX-MailScanner-From: olly@lfix.co.uk X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.056 required=5 tests=[AWL=0.006, FORGED_RCVD_HELO=0.05] X-Spam-Level: X-Archive-Number: 200510/210 X-Sequence-Number: 19282 On Tue, 2005-10-18 at 01:29 -0400, Tom Lane wrote: > "Thomas F. O'Connell" writes: > > But cleaning out /tmp seems to be a part of institutional practice on > > Linux, > > I'm unconvinced of that. A quick test on Fedora Core 4 shows that > random files in /tmp survive reboot, and any moment of thought would > show why users would object to a blanket cleanout policy. ... > I think what you've got is a rogue, broken mountnfs.sh script. I don't > even see any such script in my installation ... what is its provenance? It's a standard part of Debian, from the package initscripts. The default policy is to clean out /tmp at boot. This can be varied by changing TMPTIME in /etc/default/rcS. -- Oliver Elphick olly@lfix.co.uk Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/A54310EA 92C8 39E7 280E 3631 3F0E 1EC0 5664 7A2F A543 10EA ======================================== Do you want to know God? http://www.lfix.co.uk/knowing_god.html