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 =3D open("/dev/null", O_RDWR);
dup2(nullfd, 0);
dup2(nullfd, 1);
dup2(nullfd, 2);
if (nullfd !=3D 0 && nullfd !=3D 1 && nullfd !=3D 2)
close(nullfd);
(taken from syslog-ng which does it properly).
Can you do that in the next release?
Thanks in advance and have a nice day!
Martin
----- Forwarded message from sacrificial-spam-address@horizon.com -----
Date: 31 Dec 2003 15:02:22 -0000
From: sacrificial-spam-address@horizon.com
To: submit@bugs.debian.org
Subject: Default pg_autovacuum config glitches
X-Spam-Status: No, hits=3D-3.8 required=3D4.0 tests=3DHAS_PACKAGE,NO_REAL_N=
AME=20
autolearn=3Dno=20
version=3D2.60-master.debian.org_2003_11_25-bugs.debian.org_2003_12_29
Package: postgresql
Version: 7.4.1-1
When /etc/init.d/postgresql is run, pg_autovacuum maintains connections
to the startup tty on fds 0, 1 and 2. When run from the console (as part
of (apt-get upgrade), this caused some hiccups to a following getty.
In any case, it's considered bad behaviour on the part of a long-running
daemon.
(If you feel this is pg_autovacuum's fault rather than the init script's,
please reassign to postgresql-contrib.)
Thanks!
----- End forwarded message -----
--=20
Martin Pitt Debian GNU/Linux Developer
martin@piware.de mpitt@debian.org
http://www.piware.de http://www.debian.org
