| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | hackers(at)postgresql(dot)org, olly(at)linda(dot)lfix(dot)co(dot)uk |
| Subject: | Re: [HACKERS] More initdb follies |
| Date: | 1999-12-11 00:20:38 |
| Message-ID: | Pine.LNX.4.20.9912100300000.760-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1999-12-09, Oliver Elphick mentioned:
> >I propose that I remove it, and that it instead be possible that you can
> >do
> >
> >root# su -l postgres -c 'initdb ...'
>
> You can already do this; this example is from the Debian package installation
> It can be quite tricky, though, since there are a number of different su
> versions around. I would prefer it if root were able to run initdb directly
Of course the user would actually invoke the su himself, so he better know
what his does.
> and set the ownerships as part of the process. The ability to run as root
> should only apply to initdb.
I don't think there is a good (let alone portable) way to set ownership of
a shell script at run time. While you could do all kinds of funny business
with file ownerships, the postgres backends will still refuse to execute.
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 1999-12-11 00:20:49 | Re: [HACKERS] More initdb follies |
| Previous Message | Peter Eisentraut | 1999-12-11 00:20:27 | Re: [HACKERS] Multibyte in autoconf |