Re: Erase cache, clean registry in Linux
On Wed, Nov 26, 2008 at 10:42, lee <firstname.lastname@example.org> wrote:
> On Tue, Nov 25, 2008 at 12:09:27PM -0800, Kelly Clowers wrote:
>> And a lot of programs (Dolphin, Nautilus, gthumb, eog, etc) have thumbnail
>> caches, which are not always cleanable from in the application. Luckily,
>> many of these programs now share the FD.O standard ~/.thumbnails/
>> directory, instead of each program doing its own thing.
> That shouldn't be there in the first place. You end up with hundreds
> of megabytes of totally useless thumbnails
They are not useless, they keep thumbnail display times reasonable.
I have used programs that generate thumbnails on the fly, per session
and it is slow and annoying.
> that even cannot be
> displayed with eog or gimp --- yesterday, I removed 350MB from
> .thumbnails and tried to disable it by leaving the directory empty
> with permissions to read and write it removed. If that doesn't help,
> I'll change ownership to root, and if that doesn't help either, I
> might have to resort to enable ACLs or to making the directory a
> symlink to a partition that is mounted r/o ... I also removed a number
> of useless directories ".xvpics" that were all over the place.
> Whatever application puts thumbnails or something else somewhere
> without telling the user about it should remove it when it's no longer
They are needed to keep display times reasonable. All programs
should use the same cache, and many do. If you have a favorite
program that does not use ~/.thumbnails, you should probably
file a bug.
> That's probably difficult to do because they would have to
> monitor all the images they create thumbnails from and modify or
> remove the thumbnails as the images are altered or deleted --- but
> that's not my problem. If they can't do it, they must not create these
well, there are some basic suggestions in the spec for deleting:
There are plenty of ways that a thumbnail could avoid deletion
with these rough guidelines. However, I am not that worried about
it. Disk space is abundant and cheap, and I can always delete it,
or set a cron job to delete every so often.