Lissa, > A couple of solutions come to mind. Probably someone could think of > something better. > Have two scripts, one in the postscripts table for boot and one not in > the postscripts table to run with updatenode. -P <scriptname> > Have a parameter that you input when you run updatenode to drive the > logic you want. You can run updatenode -P "script parm1 parm2.."
Thanks for your input. We have been able to create a postscript now that does the job. It detects when it is run from outside of updatenode (that is during install) and also when a user specifies a manual override flag as an option. A normal updatenode command takes no action - so when all the postscripts are run it does nothing. Just a thought, apart from the install stage and updatenode command is there any other way postscripts are triggered to run? If there are it might trigger this script to be run. Thanks, Craig. ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
