Skip site navigation (1) Skip section navigation (2)

Re: postmaster blues after system restart

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org,Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
Subject: Re: postmaster blues after system restart
Date: 2005-10-18 05:29:31
Message-ID: 26905.1129613371@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Thomas F. O'Connell" <tfo(at)sitening(dot)com> 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 do see this in a quick grep of Fedora RC files:

/etc/rc.sysinit:rm -f /tmp/.X*-lock /tmp/.lock.* /tmp/.gdm_socket /tmp/.s.PGSQL.*

but this happens well before any of the /etc/rc.d files get to run.

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?

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Thomas F. O'ConnellDate: 2005-10-18 05:44:37
Subject: Re: postmaster blues after system restart
Previous:From: Thomas F. O'ConnellDate: 2005-10-18 04:17:49
Subject: Re: postmaster blues after system restart

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group