On Fri, 23 Sep 2011, John R Pierce wrote:
did the system run some sort of fsck autorepair when it restarted? thats
about the only thing I could think of that might have messed with the
permissions.
The file system is ext3 so it did restore from the journals.
Anyway, now I know if I shou
On 09/23/11 2:14 PM, Rich Shepard wrote:
When it started and worked I assumed that was the case. But, I've not
before had directory permissions change when a system crashed.
Cue the "Twilight Zone" theme.
did the system run some sort of fsck autorepair when it restarted?
thats about th
On Fri, 23 Sep 2011, John R Pierce wrote:
Indeed, 700 are the correct privs.
John,
When it started and worked I assumed that was the case. But, I've not
before had directory permissions change when a system crashed.
Cue the "Twilight Zone" theme.
Thanks,
Rich
--
Sent via pgsql-general
On 09/23/11 1:48 PM, Rich Shepard wrote:
My server just crashed because a CPU-intensive build threatened to
overheat the processor so the system shut down. When I rebooted and
tried to
start postgres the attempt failed because `data directory
"/usr/local/pgsql/data" has group or world access'
My server just crashed because a CPU-intensive build threatened to
overheat the processor so the system shut down. When I rebooted and tried to
start postgres the attempt failed because `data directory
"/usr/local/pgsql/data" has group or world access'. As far as I can recall,
it's always been 7
