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

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: BUG #7559: syslogger doesn't close stdout and stderr
Дата
Msg-id 505AC648.7050400@vmware.com
обсуждение исходный текст
Ответ на Re: BUG #7559: syslogger doesn't close stdout and stderr  (Reinhard Max <reinhard@m4x.de>)
Ответы Re: BUG #7559: syslogger doesn't close stdout and stderr
Список pgsql-bugs
On 20.09.2012 00:05, Reinhard Max wrote:
> On Wed, 19 Sep 2012 at 12:39, Tom Lane wrote:
>> reinhard@m4x.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: BUG #6412: psql & fe-connect truncate passwords
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: BUG #7556 addition info