This one bit me pretty badly not so long ago when it filled up the
partition I had installed upon.
Freeing up the space used is in /var/pkg/download is painfully slow when
it's grown quite
big because the content is split into a zillion fragments using what
appears to be some
kind of hashing mechanism.
I guess I'm missing part of the bigger picture but.................
What I don't really understand is what purpose this serves: Even when
flush-content-cache-on-success is enabled, the cache doesn't get flushed
in the even
of a failed installation, only on success. What's the purpose of keeping
the content around
after a successful installation?
Cheers,
Niall.
Shawn Walker wrote:
Darren Kenny wrote:
I took a look around, and noticed that the /var/pkg/download
directory appeared
to be consuming more than the actual OS itself...
...
This then made me wonder why this isn't on by default? Or why there
isn't at
least some sort of limiter on the cache, rather than letting it grow
so large.
...
It also made me think that we really should have a pkg command that
allows you
to purge this cache on demand rather than doing a :
rm -rf /var/pkg/download
Related RFEs on defect.opensolaris.org:
2266 want command-line control over content cache
6353 option to put download cache on alternate filesystem
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
