On 10/ 5/09 03:21 PM, Shawn Walker wrote:

See man pkg(1):

  property [-H] [propname ...]
          Display image property information.  With no argument, display the
          names and values for all image properties.  If a specific list of
          property names is requested, display the names and values for those
          properties.  With -H, omit the headers from the listing.

When it said "image property" I thought it meant just that. Does this mean
that flush-content-cache-on-success is not a pkg property? Confusing :-).
$ pkg property

# pkg property
PROPERTY                       VALUE
send-uuid                      True
preferred-publisher            dev.opensolaris.org
require-optional               False
flush-content-cache-on-success true
display-copyrights             True
pursue-latest                  True

So, if you were expecting the /var/pkg/download in your original boot
environment to be purged, it won't be. However, if you check the new
boot environment's /var/pkg/download, it should be empty ...

But the reverse actually occurred. At the start it was empty and there
were no old BEs, snapshots, or clones to hide any in. After the install
/var/pkg/download was definitely not empty, and the cache flag was set.

No, these are unofficial. There are RFEs open to document and enhance
control over the download cache.

Fair enough, although I am partial to the sxce solution which lets you
move all of /var. If you are so constrained for space (e.g., 16GB boot
disk) that you need to move the download cache, you'll probably be
moving /var/dump, /var/crash, and swap anyway, so why not move
them all?

Cheers -- Frank

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

Reply via email to