On Sat, 27 Mar 2004, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> > The postmaster's seems to have a section that does a null device open,
> > dup2s and a close at the end of pmdaemonize in the 7.4 and 7.5 versions on
> > my box:
>
> Yes, and that behavior is exactly why we depre
Stephan Szabo <[EMAIL PROTECTED]> writes:
> The postmaster's seems to have a section that does a null device open,
> dup2s and a close at the end of pmdaemonize in the 7.4 and 7.5 versions on
> my box:
Yes, and that behavior is exactly why we deprecate -S ... I don't think
that the autovacuum daem
On Fri, 26 Mar 2004, Matthew T. O'Connor wrote:
> Bruno Wolff III wrote:
>
> >On Thu, Mar 25, 2004 at 16:08:49 +0100,
> > Martin Pitt <[EMAIL PROTECTED]> wrote:
> >
> >
> >>A while ago we received the bug report below against pg_autovacuum.
> >>Since it runs as a daemon, it should detach from its
Bruno Wolff III wrote:
On Thu, Mar 25, 2004 at 16:08:49 +0100,
Martin Pitt <[EMAIL PROTECTED]> wrote:
A while ago we received the bug report below against pg_autovacuum.
Since it runs as a daemon, it should detach from its controlling
terminal by executing sth like
int nullfd = open("/d
On Thu, Mar 25, 2004 at 16:08:49 +0100,
Martin Pitt <[EMAIL PROTECTED]> wrote:
> Hi PostgreSQL hackers!
>
> A while ago we received the bug report below against pg_autovacuum.
> Since it runs as a daemon, it should detach from its controlling
> terminal by executing sth like
>
> int nul
Hi PostgreSQL hackers!
A while ago we received the bug report below against pg_autovacuum.
Since it runs as a daemon, it should detach from its controlling
terminal by executing sth like
int nullfd = open("/dev/null", O_RDWR);
dup2(nullfd, 0);
dup2(nullfd, 1);
dup2
