Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)
Date
Msg-id 20793.1521319636@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c)  (Christoph Berg <myon@debian.org>)
List pgsql-bugs
Christoph Berg <myon@debian.org> writes:
> Re: Andrew Gierth 2018-03-17 <87in9uhbco.fsf@news-spur.riddles.org.uk>
>> Tom> I think your example of "sudo /usr/bin/pg_ctl" is pretty
>> Tom> artificial; who'd bother spelling that out?
>> 
>> Not necessarily exactly like that, but we do occasionally get this issue
>> coming up on the IRC channel.

> It's absolutely not artificial. I can easily trigger the message from
> my home directory:

> $ chmod 700 .
> $ sudo -u postgres psql
> could not change directory to "/home/cbe": Permission denied

No, I think you missed my point: I thought typing "sudo ... /usr/bin/pg_ctl"
rather than just "sudo ... pg_ctl" seemed artificial.  Your example
doesn't exactly contradict that.  It's relevant here because it affects
whether or not argv[0] is already an absolute path.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Christoph Berg
Date:
Subject: Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c)
Next
From: Petar Bogdanovic
Date:
Subject: Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution(exec.c)