On 10/ 8/09 03:31 PM, Shawn Walker wrote:
When you say it doesn't work, that mean that after rebooting the system to the new boot environment, you checked the contents of /var/pkg/download, and it wasn't empty?
Yes
Or did you execute "pkg image-update" and then immediately check the contents of /var/pkg/download?
No. I should add that that it completed far too quickly on the second pass to have had time to flush the cache.
flush-content-on-success should already account for beadm failure (note that it doesn't actually use beadm literally, it uses libbe, the same library that beadm uses to manage the system).
Scratch that idea then. Other than the unlikely true != True there doesn't seem to be an explanation. When b125 shows up I'll try it again - doubtless it will work, and we'll put it down to some unknown cause. Thanks for taking the time to discuss it. Is there anything in particular that it would be helpful to look at in case it doesn't work next time?
Cheers,
_______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
