Adding a check to verify that the environment is not the BOOTCD will prevent a

NodeUpdate from starting the NM.  I think NM starting in the boot cd may be
causing some of the rpmdb corruption seen in /vservers/

diff --git a/NodeManager.spec b/NodeManager.spec
index c1efbd4..2ddcc27 100644 (file)
--- a/NodeManager.spec
+++ b/NodeManager.spec
@@ -53,7 +53,9 @@ chkconfig --add conf_files
 chkconfig conf_files on
 chkconfig --add nm
 chkconfig nm on
-service nm restart
+if [ "$PL_BOOTCD" != "1" ] ; then
+       service nm restart
+fi
 
 
 %preun