Patrick Begou <[email protected]> wrote: > Rob wrote: >> Patrick Begou <[email protected]> wrote: >>> Seamonkey is again writing continuously to addons.sqlite-journal file! >>> Nearly >>> 50Mbit/s. >>> And there is only one seamonkey process (seamonkey mail) runing. >>> If I stop it, IO stop, so it is seamonkey. But why ? >> NOTE! >> >> It is not possible, NOT POSSIBLE, to have the .sqlite files of >> seamonkey (or any other .sqlite files) on NFS storage! Neither >> on SMB storage, for that matter. >> Doing so will lead to corruption, failure to apply the journal >> file, etc. Precisely what you mention. >> >> You should copy them to the local disk, let seamonkey work with >> them there, and copy back on logout. >> > But how can you setup this when all the home directories are accessed via NFS > ? > All the storage is in the datacenter for security purpose (raid array of > disks > on two redundant NFS servers in a secured room). This also allows standart > client configuration with no local user data. > > Patrick
I tried many times like you and no matter if I use Windows or Linux, the sqlite does not work correctly on network file systems. We have used Seamonkey a long time on Windows in an environment like that, but on Windows the user profile is copied from the network to the local disk on login, and back to the network on logout. Then it works OK. I tried running scripts to manipulate the .sqlite databases while they are on the network storage, e.g. to delete unwanted cookies, but it always failed. When first copying to a local disk, or running the script on the server where the files are local, it is OK. I don't know a solution when home directories are on the network. > NB: as said in the previous mail, the problem seams solved and related to the > chatzilla addon installed by this user. chatzilla is not an addon installed by the user, it comes as standard with Seamonkey. Maybe this user was the only one actually using it. However, when you look on your storage you will find many .sqlite-journal files. Those will normally not exist after the program exits. Only on network storage they remain. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
