Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Adding a --quiet option to initdb

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Devrim GUNDUZ <devrim(at)commandprompt(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Adding a --quiet option to initdb
Date: 2006-01-25 19:15:34
Message-ID: 4969.1138216534@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Greg Stark <gsstark(at)mit(dot)edu> writes:
> I always wondered why the Redhat init scripts thought it was a clever idea to
> redirect the output to /dev/null. It seems like a pessimal user interface
> choice. Every time I have to work with a Redhat machine where Postgres isn't
> starting up the first thing I have to do is edit the init script so I can what
> the problem is.

Yeah, that's finally fixed in the latest versions.  The problem was that
sending the postmaster log into a file wasn't a good long-term idea
because of the lack of any way to rotate the log.  Current RPMs set up
redirect_stderr with some reasonable rotation options instead.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: James William PyeDate: 2006-01-25 19:20:38
Subject: Re: Adding a --quiet option to initdb
Previous:From: Greg StarkDate: 2006-01-25 19:09:16
Subject: Re: Cleaning up the INET/CIDR mess

pgsql-patches by date

Next:From: James William PyeDate: 2006-01-25 19:20:38
Subject: Re: Adding a --quiet option to initdb
Previous:From: Peter EisentrautDate: 2006-01-25 19:08:49
Subject: Re: Adding a --quiet option to initdb

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group