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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christoph Berg <myon(at)debian(dot)org>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, petar(at)smokva(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)
Date: 2018-03-17 20:47:16
Message-ID: 20793.1521319636@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christoph Berg <myon(at)debian(dot)org> writes:
> Re: Andrew Gierth 2018-03-17 <87in9uhbco(dot)fsf(at)news-spur(dot)riddles(dot)org(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Petar Bogdanovic 2018-03-17 20:55:44 Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)
Previous Message Christoph Berg 2018-03-17 20:40:51 Re: BUG #15120: use of getcwd(3)/chdir(2) during path resolution (exec.c)