Re: refdb-init.sh update

Rich Shepard <[email protected]> was heard to say:

> sed: invalid option -- E

Oh dear. This is another BSDism. I'll have to rewrite this using the basic
regular expressions.

>    Running as a mere user, I have no write permissions to /usr/local/etc/.
> That's why refdbdrc could not be created. Root has such write permissions,
> but I don't want to create the working bibliographic database under root's
> account.
>

I'm afraid the script won't work unless you're root. You need to create or
modify files which are read-only for regular users. Regarding the root account,
there are two (almost) orthogonal concepts at work here. The first is your
authentication against the OS, the second is the authentication against the
database engine. Creating the database as OS user root does not mean that you
cannot access it from database engine user rich. RefDB will grant a regular
database engine user the appropriate permissions to work with the database. You
cannot delete a database as a regular database engine user though, that's why
you usually set up refdba to connect with the database engine superuser name.
The only link between the two concepts is that PostgreSQL can be set up to
allow connections to the database engine superuser only from a particular OS
login account. E.g. Debian uses this trick to enhance security. You have to su
postgres before you can connect as the database engine user postgres.

Rest assured that you have picked the most difficult combination to set up, but
I think we'll get this done eventually. I'll post another update of the script
tonight which fixes the sed problem. If you run as root then, the setup will
hopefully work.

regards,
Markus

-- 
Markus Hoenicka
[email protected]
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de