From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Patch to be verbose about being unable to read |
Date: | 2003-06-21 12:50:15 |
Message-ID: | Pine.LNX.4.44.0306211430320.1882-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Sean Chittenden writes:
> Agreed, though one train of thought is that if someone did put a
> .pgpass file in place that isn't readable, it should be known that
> their efforts are being wasted in vein.
I tried making several dot-files I found in my home directory unreadable
(or unsearchable, in case of a directory): acrorc, antrc, bashrc, cvsrc,
fetchmailrc, inputrc, licq, mozilla, psqlrc, rpmmacros, Xmodmap, xemacs,
xmms. Bash gave me warning, fetchmail gave me an error (which is
reasonable, because fetchmail doesn't work without configuration), and the
rest just ignored the file.
Open password and private key files might give different results, but as
far as unreadable files go, I say ignore them.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Björklund | 2003-06-21 15:26:42 | Patch for psql to avoid altering the PGresult strings |
Previous Message | Joe Conway | 2003-06-21 04:20:03 | Re: connectby(... pos_of_sibling) |