Re: [PATCHES] Adding a --quiet option to initdb
От | Greg Stark |
---|---|
Тема | Re: [PATCHES] Adding a --quiet option to initdb |
Дата | |
Msg-id | 87y814tc47.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | Re: [PATCHES] Adding a --quiet option to initdb (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: [PATCHES] Adding a --quiet option to initdb
|
Список | pgsql-hackers |
Bruce Momjian <pgman@candle.pha.pa.us> writes: > Devrim GUNDUZ wrote: > > Hi, > > > > On Wed, 2006-01-25 at 11:28 -0500, Tom Lane wrote: > > > Devrim GUNDUZ <devrim@commandprompt.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. -- greg
В списке pgsql-hackers по дате отправления: