On Monday 20 May 2002 14:17, Peter Billson wrote:
> Phil,
> I am running Mozilla in a public library and had similar requirements.
> I am not sure this is the best solution, but it works well.
>
> After running the browser once for each user to set everything up, I
> made the each user's .mozilla directory immutable (chattr -R +i) with
> the following exceptions:
> (These are all under .mozilla/{user}/{gobbldy-gook}/)
>
> I linked cookies.txt -> /dev/null then made it immutable
> I linked history.dat -> /dev/null then made it immutable
>
> For SSL to work the following 4 files are *not* made immutable
> (chattr -i)
> secmod.db
> secmodule.db
> cert7.db
> key3.db
>
> I let the Cache work as normal in the users home directory, although
> your idea of using /tmp would be fine too.
>
> I also linked the bookmarks.html to one central bookmark file to make
> my life easier.
>
>
> This set up allows the user to do anything they want (set bookmarks,
> change preferences, etc) but none of the changes will be saved on exit.
>
>
> Pete
Folks,
I just installed Mozilla 1.0 and after deliberately crashing a client while
running Mozilla, found that the browser refused to start because it thought
the profile was already in use. I followed the above instructions, and now
mozilla is crash proof.
This was a timely hint!
Thanks,
Skip
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
