| From: | "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
| Cc: | darcy(at)druid(dot)net, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] getcwd failing suddenly |
| Date: | 1999-01-22 15:45:50 |
| Message-ID: | m103imM-0000bnC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thus spake Tom Lane
> > shell-init: could not get current directory: getcwd: cannot access parent directories
>
> A quick glimpse scan shows no such error message in the Postgres
> sources. This must be coming out of your shell. Protection change
> on one of the ancestors of your home directory, maybe?
I forgot to mention that this happens on 3 different machines as I
upgrade to the latest PostgreSQL and each machine has a different
version of the OS. I can't recall changing anything to do with
directory permissions but I certainly didn't change all 3.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Gartland | 1999-01-22 16:09:39 | Alpha Size (size_t) != int problem |
| Previous Message | Al Dev | 1999-01-22 15:45:28 | Move PostgreSQL 6.4.2 RedHat RPM packages to proper locations |