Has anyone else seen this behavior? The other day, I created a boot
environment, patched it with 150 patches, and then activated it about
four hours later. I was very pleased to see it reboot into a fully-
patched system with only a few minutes of downtime. However, files
that were listed in the synclist file weren't synchronized. A good
example is this one, from /etc/lu/synclist:
/var/adm/hourlystats.log OVERWRITE
This file has one line appended once an hour. On the newly-booted
boot environment, it had a gap of four hours. At the time I ran
`luactivate', it reported:
A Live Upgrade Sync operation will be performed on startup of boot
environment <secndlu>.
WARNING: The following files have changed on both the current boot
environment <firstlu> zone <global> and the boot environment to be
activated <secndlu>:
/var/adm/hourlystats.log ...
... /var/spool/mqueue/qd09/qfmBDFRK4t016080
INFORMATION: The files listed above are in conflict between the current
boot environment <firstlu> zone <global> and the boot environment to be
activated <secndlu>. These files will not be automatically synchronized
from the current boot environment <firstlu> when boot environment
<secndlu> is activated.
How could it have been updated on the new BE? There shouldn't have been
a conflict. This was done on Solaris 10 5/08.
--
This message posted from opensolaris.org
