[Users] changes in database setup scripts

[Ovidiu Sas]

The location of openserctlrc is dictated by the make options:
$(cfg-prefix)/$(cfg-dir)/openserctlrc (see install script).

If the script is not able to modify the openserctlrc file, maybe it
should ask for root password or just print a BIG warning that the
openserctl file needs to be modified.

As an alternative, we could have the test in openserctl, but I think
that it really belongs to the db install script.


Also, the db install script should check/change the DBENGINE too :-)
If DBENGINE is not set, then set it
If the DBENGINE is set and it matches the install script, proceed,
otherwise, exit with error: Trying to install a db that doesn't match
DBENGINE!!! Fix your openserctlrc file.



Regards,
Ovidiu Sas

On 5/31/07, Henning Westerholt <henning.westerholt at 1und1.de> wrote:
> On Donnerstag, 31. Mai 2007, Ovidiu Sas wrote:
> > If the serweb table is installed or not has an impact on how
> > openserctl operates while adding users.
> > I was thinking about adding the following enhancement to the db
> > install script:  if the serweb table is installed, perform a sed
> > replace operation on openserctlrc for HAS_SERWEB.
> > This will avoid the manual step of setting HAS_SERWEB and people
> > asking the same question over and over on the mailing list.
>
> You're right,
>
> this questions gets annoying.. But the user probably don't run this setup
> script with root privileges, that are needed if you want to modify the
> systemwide openserctlrc. And the user can install the rc file in at least
> three different places.
>
> Perhaps we can detect in the openserctl script that the user has serweb
> installed (e.g. try an select on admin_privileges), and set internally this
> variable?
>
> What do you think?
>
> Henning
>