On Wed, 2011-04-27 at 10:19 +0200, =?UTF-8?Q? Bj=C3=B6rn_T. ?= wrote:
> Hi
> maybe some one can give me a hint on opengroupware read/write configuration.
> There is a opengroupware installation with some hundret users. To work on a
> migration I want that noone has write acces for a period of days but still
> can login an view the appointments already in the database.
> What would be the right way to do this? And how can I achieve that?
To my knowledge there is no quiescent / read-only mode [although that is
a good idea; I'll make it a feature request for OpenGroupware Coils].
Probably the best thing you can accomplish is the lock down database
permissions; attempts to modify the data will fail with ugly errors but
the app should continue to function. Just revoke INSERT, UPDATE, and
DELETE on all tables except "log" and "session_log" to the account the
OpenGroupware daemons' connect as. The daemons needs write privileges
to "log" and "session_log" in order to run.
|
