Joe, I hope you don't mind my replying this to the list, in the interest of the discussion. On 5/4/06, Joe <[EMAIL PROTECTED]> wrote:
G. Roderick Singleton wrote: > On Tue, 2006-05-02 at 11:42 +0300, Alon Keren wrote: > >> On 4/12/06, CPHennessy <[EMAIL PROTECTED]> wrote: >> >>> On Tue April 11 2006 11:16, + Alon Keren wrote: >>> >>>> System: Linux (LFS) >>>> OOo version: 2.0.0rc3 >>>> >>>> I wish to prevent users from altering their OOo directories >>>> (~/.openoffice.org2) and from saving files in them. >>>> To that end, I supply a user with a ready-made '~/.openoffice.org2', and >>>> disallow any write-access to it and its contents. >>>> >>>> A problem occures when I edit a file (.odt, .ods), save it, and then exit >>>> OOo: After exiting I get the following pop-up dialog: >>>> 'Error saving the document: >>>> user-home-dir/.openoffice.org2/user/basic/script.xlc/ >>>> General Error. >>>> Genereal input/output error.' >>>> When I press 'OK', it repeats, only with 'dialog.xlc' instead of >>>> 'script.xlc '. >>>> >>>> Apparently, OOo tries to replace those two files with something of its own >>>> making, so placing ready-made files is not an option. >>>> >>>> Does anyone know of a way to go around this, either by means of configuring >>>> the already-installed OOo, or by means of altering the >>>> source-code/installation process? >>>> >>> Hi Alon, >>> Can you please upgrade to 2.0.2 and try again. >>> >>> >> I've just finished compiling 2.0.2 and, unfortunately, the issue persists. >> >> > > Did you alter the sources? I expect not as these files are expected to > be writable. >
I did alter the sources, only to make OOo compile on my system (based on http://www.linuxfromscratch.org/blfs/view/svn/xsoft/openoffice.html). To the best of my knowledge, it shouldn't alter behaviour. Do you have anything specific in mind?
I don't know any specifics, but poking around it various "prefs" files (that would be stored in the same place), I have found that that's where applications keep history - things like recently opened files, session variable, etc. that need to be saved quite often.
In all that poking, did you hapen to find a way to change the place where such files are kept? I wouldn't mind keeping them elsewhere, but the OOo's directory must remain the same.
Since it looks like you're on Linux, you might try turning off execute (and maybe write - that might not work) permissions for this directory and just turning on write permission for those particular files that have to be accessible. That would minimize your exposure.
I wish to have no write-access at all to OOo's directory, including those files. Regardless, giving write-permissions solely to these files wouldn't work, as they are actually removed and then re-created - and not simply written to. To allow this I would have to give write-permissions to the directory which contains them - something which I'm not interested in.
Another approach would be to leave things wide open and write a script that could be run as needed that would overwrite that directory from a saved "template" (possibly leaving a few user files intact).
That's an interesting thought, but something that I personally could not adopt, for the reasons specified before. I would imagine that, if no relevant OOo preferences exist, source-code manipulation could do the trick. If only one would know where to look for.
Of course, educating users, however daunting the task (after all, that's part of what we do on this list), is an option not to be ignored - especially if you or someone in authority can impress upon them the need for compliance with standards. Joe
I hope it wouldn't have to come to this. P.S. Please CC me any replies, as I'm not subsribed to this list, --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
