order of installation and reboots using smpatch/updatemanager

Using updatemanager it tells me it has installed a certain set of patches and that others require a reboot and will be installed then - fine. I can then download and install further patches as long as any dependencies are met.

But if I download the patches using smpatch I get an information file telling me the order in which patches should be installed and where reboots are needed. Here's an example:

patchpro_dnld_2006.07.24@17:47:18:EST.txt

::::::::::::::

This patch bundle was generated by PatchPro.

Please refer to the README file within each patch for installation

instructions. To properly patch your system, the following patches

should be installed in the listed order:

1) 120887-06

2) 118557-05 !!! IMMEDIATE REBOOT !!!

3) 122027-04 !!! IMMEDIATE REBOOT !!!

4) 122856-02

--

Now my reading of the above is that I should install 1) then 2) do a reboot, install 3) and do a reboot then install 4) - as that is the listed order. And if I don't do this then I have installed the patches properly

But running smpatch update it installs 1) and 4) straight away and reports that 2) and 3) will be installed at next reboot:

Installing patches from /var/sadm/spool...

120887-06 has been applied.

NOTICE: Patch 118557-05 cannot be installed until the next system shutdown.

NOTICE: Patch 122027-04 cannot be installed until the next system shutdown.

122856-02 has been applied.

And at next reboot there is only a single reboot and both patches are applied.

So what's with the instructions in the patchpro* file? Are these just overly conservative guidelines or what?

Thanks.

[1716 byte] By [davidholmes] at [2007-11-26 8:58:56]
# 1

If patch 4 is not dependant on either patch 2 or 3 then there's no problem installing it before either 2 or 3.

However sometimes I have seen an error:

ALERT: Failed to install the patch {0} xxxxxx-xx

which I believe means that the patch has a dependency on another patch which can't be installed because it needs an immediate reboot.

After doing the reboot you might find that you can go back and run in these extra patches which caused the error the first time around.

Just my interpretation for what it's worth.

john.

INSJohn at 2007-7-6 23:01:32 > top of Java-index,Administration Tools,Sun Update Connection-System...