What is the proper procedures for moving third party xml out of the way and or regenerating the order for SMF when a patch I suspect the kernel patch either 120011-14 and or 127111-03+ changes dependencies.
I can't confirm this but I suspect there were changes made to the SMF with the new kernel patch 120011-14 and or 127111-03+ else dependencies were introduced that no longer make customer's 3rd party scripts work upon boot. After the latest kernel patch, I see a number of cases where the SMF particularly milestone multi-user no longer can boot to an online state. It either gets stuck in offline or maintenance and unless we take 3rd party stuff out of the picture I can't get around it. I noticed dependency issues in the *manifest*.log. I figured a way to get the customer's system up and running but it seems more like a hack to me and I need advice on a better way to do this. I was thinking perhaps there is a svccfg export and or delete or something that could be done to regenerate the SMF order. Is there anything like this and or should I suggest an RFE? My question is.... How to move SMF 3rd party xmls <repository stuff> out of the way when you see error in the manifest logs? Here is what I did to get around my customer's issue but I know there has to be a better way to get around this. # mv /var/svc/manifest/application/coldfusion.xml /var/svc/holding # /lib/svc/bin/restore_repository choose seed since I had customer backup stuff # init 6 # mv /var/svc/holding/coldfusion.xml /var/svc/manifest/application Have the customer reimport the script into SMF, verify and reboot. I would think there is a better way to do this. -- ============================================================================ S U N M I C R O S Y S T E M S I N C. Jill Manfield Technical Support Engineer email: jill.manfield at sun.com phone: (800)USA-4SUN (Reference your case number) Mgr: joel.fontenot at sun.com Submit, View and Update tickets at http://www.sun.com/service/online ============================================================================