On 02/28/12 07:27, Frank Batschulat wrote:
On Tue, 28 Feb 2012 16:18:12 +0100, Shawn Walker
<[email protected]> wrote:

On 02/28/12 06:14, Frank Batschulat wrote:
friends, this topic has been probably beaten to death, but....

I have 1 system running s11u1 build 10 with only this and a 2nd be of
build 8 (I only keep 2 while updating to every build).

its /var/pkg just keeps growing and its now at 3.7GB
of course it has this enabled:

flush-content-cache-on-success True

on the other hand my 2nd system also running s11u1 build 10 only
shows 1.6G size of /var/pkg...still large, but it does apparently
shrink from update to update again, while the other systems just
keeps growing. to wit, the system which behaves resonably does even have
much more stuff installed then the other growing system.

so where to look at in /var/pkg what can be deleted so I gain space
back ?

You can delete any of the 'file' directories from /var/pkg/publisher.

thanks !

(It would be interesting to see how big they are first before doing
that though.)

It could be your system is old enough that it also has accumulated
manifests from older builds before it was changed to automatically
remove unused manifests during updates/uninstalls as well.

Again though, without seeing a breakdown of the sizes of the
directories in /var/pkg/publisher, it's difficult to say.

it appears that its all in:

3.3G solaris/file

entire list from /var/pkg/extra and /var/pkg/solaris at the end.

I'll leave that system for now that way in case you want to know
anything specific.

So here's the catch about flush-content-cache-on-success. It flushes the cache in the live BE. This means that for older systems that have been upgraded over time, you'll be stuck with older bits hanging around for much longer.

So remove the /var/pkg/publisher/solaris/file directory and going forward, it shouldn't grow as much.

-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to