On 12/10/2012 11:53 AM, A Williams wrote:
> Backing up my /home directory under Linux, I noticed that it spent a few
> minutes backing up my Seamonkey Cache. This is *not* time well spent so
> I decided to do something about it.
>
> Preferences -> Privacy and Security.
> I checked 'Always clear my private data when I close Seamonkey' and
> 'Cache'. Problem solved! All I have to do is leave Seamonkey (which I
> do anyway) before taking a backup and all will be fine.
>
> No.
>
> Instead of actually deleting my Cache, Seamonkey helpfully renamed the
> Cache directory as Cache.Trash[10-digit-number]. Which I then spent
> several minutes backing up.
> What is the point of this behaviour? The option is under "Privacy and
> Security". Just renaming the contents is neither.
>
> Seamonkey 2.14, the 64-bit Linux version.
>
> I have had this option set for months at work (Windows 7 x 32) so I need
> to see if I have 0, 1 or n similar directories there. Tomorrow.
>
Interesting. I checked on a 64-bit linux system:
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101
Firefox/17.0 SeaMonkey/2.14.1
Build identifier: 20121129230834
that I had used yesterday, and found 11MB of cache files. I have
everything checked to clear at shutdown with the exception of 'Saved
Passwords'. Using:
$ du -cSh
...
11M total
So I opened SeaMonkey (2.14.1) on that machine today, opened a few pages
in tabs & closed again (ensuring that I check 'Clear Private Data Now' &
shut down SeaMonkey. This time the cache is cleared & I end up with 136K:
$ du -cSh /home/<user>/.mozilla/seamonkey/<snip>.default/Cache
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/4
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/2
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/C
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/3
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/6
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/0
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/A
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/F
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/1
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/9
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/8
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/B
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/D
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/5
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/7
4.0K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache/E
72K /home/<user>/.mozilla/seamonkey/<snip>.default/Cache
136K total
I'll have to check more often to see if the 11M cache was a problem with
SeaMonkey or "Operator". I was using NX between machines yesterday & in
at least one instance I killed SeaMonkey ($ killall seamonkey) rather
than shutting down properly. So it's quite possible that the 11M was
from the killall instead.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
