| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas F. O'Connell | 2005-10-18 05:44:37 | Re: postmaster blues after system restart |
| Previous Message | Thomas F. O'Connell | 2005-10-18 04:17:49 | Re: postmaster blues after system restart |