Hi,
Christian Andersson wrote:
I've been away doing other stuff for a while, so please forgive that I'm so late in answering :-)
Please see comments inline. (I've been doing some research after reading your answer)
You sure have :-)
Joerg Barfurth wrote:You need a decent OS/file system, so that you can prevent your users from changing files in the OOo program installation (or another directory).
At the time of writing I only knew of 2 places where this could take plase, in the shared registry and in the user registry, ofcourse we can lock the file in the user registry (we cannot use the shared registry since not all users should have the restrictions)
This wasn't clear from your request.
so that only an administrator can read them, but this works only for the Commands.xcu file and not for any of the other configuration files where parts might be changeable by the user and parts by the administrator. just read on, no need to comment .-)
If you install configuration data as (shared or user-specific) UNO packages it goes into yet other locations. Nevertheless it gets kind of ugly, because you have to first install the package as the user and then change the file access. Your solution below is better.
Even now OOo merges data from multiple locations. These locations all use the same file-based backend. Of course the files holding the user preferences need to be placed in a user-writable location. But the files holding default values can (and should) be placed in a location that is not writable by the user. By default this is under the OOo installation directory. With a standard multi-user installation this will be non-writable for ordinary users both on un*x systems and on Windows 2000/XP (with NTFS and appropriately restricted user accounts).
in the configmgrrc file for Openoffice there is a CFG_strata line that I thought I could use to solve my problem.
That ought to work.
if I add my own path in this line just before the userpath declaration
I should be able to do the things i want. I've tried it and it works, HOWEVER there is a smal problem... it looks like I can only add paths that starts with a configuration value?
for example CFG_UserLayerUrl=$UserInstallation/user/registry CFG_MyLayerUrl=$UserInstallation/mydata/registry
CFG_LocalDataSvc=com.sun.star.comp.configuration.backend.LocalStratum
CFG_Strata=[...];${CFG_LocalDataSvc}:$CFG_MyLayerUrl;${CFG_LocalDataSvc}:$CFG_UserLayerUrl;
will work, however changeing CFG_MyLayerUrl to for example /opt/mydata/registry
Openoffice will not start anymore..
Note that they are all named ..Url for a reason: You need a file URL instead of a system path. Try '${CFG_LocalDataSvc}:file:///opt/mydata/registry;'.
BTW: You don't ned to define a variable for each layer. And the directory need not be named 'registry'. But you need the 'data/org/openoffice/...' hierarchy inside.
is there some way to specify Absolute url:s here?
Yes. Use one ;-)
or do I always have to base it on a specified variable? $BaseInstallation/$UserInstallation/etc ?
and is there a way to specify the user-id into this? I'd would like to be able to write
CFG_MyLayerUrl=/opt/mydata/$user/registry
If I'm not mistaken, you actually can use environment variables in that file. Beware: You may get into problems, if your user-ids or directories have non-ASCII characters in them.
HTH, J�rg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
