delayed patching broken?
I noticed that some patches which had been delayed to shutdown arent being installed.
After a lot of mucking around, it appears that the "installupdates" script is no longer being called as part of the shutdown sequence.
The change happened with patch 121086-01.
And I can verify that pre patch the installupdates script is linked into
/etc/rc0.d/K51installupdates
And after the patch, it still exists in the /etc/init.d directory but isnt linked into the /etc/rc0.d, /etc/rcS.d etc directories.
Assuming I havent missed something obvious, this appears to be a bug. I can log a bug report if necessary. But I won't bother if this is a know problem.
# 1
We have replicated the problem you are seeing, the installupdates init script is no longer present in /etc/rc0.d after applying patch 121086-01 (which was released on the 19th October).
The patch appear to have been for a performance bug 6322616 to correct the installupdates script as a start-up script. It does not appear to have been released by the Sun Update Connection development team however.
We will raise this matter for withdrawl and correction of the patch.
# 2
We have experienced this identical problem.
I didn't do anything special to get the 121086-01 patch. I just selected all the patches that were available. So, it must have been part of the collection of patches that Update Manager acquired as part of its behavior.
I appreciate that SUn is working on a fix. However, in the mean time, is it OK to simply recreate the links (in /etc/rc0.d and /etc/rcS.d) to /etc/init.d/installupdates?For example, create /etc/rc0.d/K51installupdates, as a (hard) link to /etc/init.d/installupdates?
Thank you.
David Grove
Message was edited by: ForumModerator
# 3
Hi there,
I ran into the same problem yesterday, and the workaround I implemented that worked like a charm is the following :
1. relinked /etc/init.d/installupdates to /etc/rc0.d/K51installupdates, and /etc/rcS.d/K51installupdates
2. brought down the box to single-mode ("init S")
and left it alone to finish it's updates, once it was done
did a clean reboot ("init 6") and everything was ok.
