On Thu, Oct 21, 2004 at 02:10:48PM -0400, Tom Lane wrote:
It was suggested to me off-list that libpq should do
fcntl(fd, F_SETFD, FD_CLOEXEC) on the socket connecting to the server.
This would prevent any child program from accidentally or maliciously
interfering with the connection. It would
It was suggested to me off-list that libpq should do
fcntl(fd, F_SETFD, FD_CLOEXEC) on the socket connecting to the server.
This would prevent any child program from accidentally or maliciously
interfering with the connection. It would also prevent people from
deliberately turning over a
On Thu, 21 Oct 2004, Tom Lane wrote:
It was suggested to me off-list that libpq should do
fcntl(fd, F_SETFD, FD_CLOEXEC) on the socket connecting to the server.
This would prevent any child program from accidentally or maliciously
interfering with the connection.
Either way that the lib sets
Dennis Bjorklund [EMAIL PROTECTED] writes:
On Thu, 21 Oct 2004, Tom Lane wrote:
It was suggested to me off-list that libpq should do
fcntl(fd, F_SETFD, FD_CLOEXEC) on the socket connecting to the server.
This would prevent any child program from accidentally or maliciously
interfering with
Tom Lane wrote:
Dennis Bjorklund [EMAIL PROTECTED] writes:
On Thu, 21 Oct 2004, Tom Lane wrote:
It was suggested to me off-list that libpq should do
fcntl(fd, F_SETFD, FD_CLOEXEC) on the socket connecting to the server.
This would prevent any child program from accidentally or maliciously
