| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Devrim GUNDUZ <devrim(at)commandprompt(dot)com> |
| Subject: | Re: Adding a --quiet option to initdb |
| Date: | 2006-01-25 19:08:49 |
| Message-ID: | 200601252008.50507.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Devrim GUNDUZ wrote:
> 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.
This is merely an opinion. On what technical grounds would it be
"better"?
(I happen to agree with Greg's post that the init script shouldn't be
silent in the first place. I'm also of the opinion that initdb
shouldn't be run from the init script, but that's a different topic.)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2006-01-25 19:09:16 | Re: Cleaning up the INET/CIDR mess |
| Previous Message | Steve Atkins | 2006-01-25 18:40:36 | Re: Cleaning up the INET/CIDR mess |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-25 19:15:34 | Re: [PATCHES] Adding a --quiet option to initdb |
| Previous Message | Thomas Hallgren | 2006-01-25 18:23:19 | Re: Adding a --quiet option to initdb |