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

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

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Devrim GUNDUZ <devrim(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:07:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:

> Devrim GUNDUZ wrote:
> > Hi,
> > 
> > On Wed, 2006-01-25 at 11:28 -0500, Tom Lane wrote:
> > > Devrim GUNDUZ <devrim(at)commandprompt(dot)com> writes:
> > > > Attached is a patch which adds --quiet and --q option to initdb.
> > > 
> > > Why is this a good idea?
> > 
> > I was playing with 8.2 RPM init script and thought that instead of
> > directing the output to /dev/null, it would be better to use a command
> > line option for that. Also, we are designing a new installer project and
> > --quiet might help us.
> OK, as long as you understand that the patch should not be applied.  "It
> might be valuable" from only one person is not enough.

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.


In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-01-25 18:08:01
Subject: Re: Cleaning up the INET/CIDR mess
Previous:From: Steve AtkinsDate: 2006-01-25 17:49:53
Subject: Re: Cleaning up the INET/CIDR mess

pgsql-patches by date

Next:From: Thomas HallgrenDate: 2006-01-25 18:23:19
Subject: Re: Adding a --quiet option to initdb
Previous:From: Bruce MomjianDate: 2006-01-25 17:54:22
Subject: Re: [GENERAL] Different exponent in error messages

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