Re: BUG #7559: syslogger doesn't close stdout and stderr

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Reinhard Max <reinhard(at)m4x(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7559: syslogger doesn't close stdout and stderr
Date: 2012-09-20 07:31:20
Message-ID: 505AC648.7050400@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 20.09.2012 00:05, Reinhard Max wrote:
> On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
>> reinhard(at)m4x(dot)de writes:
>> And what makes /dev/null necessarily the right substitute?
>
> Because it is what virtually all deamons have been doing for the last
> 3..4 decades?
>
>> I don't think we should change this within Postgres. We removed logic
>> associated with daemonization altogether in 9.2
>
> Huh - why that?

I believe Tom is referring to the removal of silent_mode in 9.2, see
http://archives.postgresql.org/pgsql-general/2011-06/msg00796.php and
http://archives.postgresql.org/pgsql-hackers/2011-06/msg02156.php. "We
removed logic associated with daemonization" meant that the logic was
removed from postmaster, because the preferred way to do it is by
calling "pg_ctl start". pg_ctl redirects to /dev/null as you'd expect.

- Heikki

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2012-09-20 08:00:42 Re: BUG #7556 addition info
Previous Message Heikki Linnakangas 2012-09-20 07:18:08 Re: BUG #6412: psql & fe-connect truncate passwords