Hi Tom, Tom Whitten wrote: > Karen, > > The warning that you are seeing is generated by the Extended Templates > project, PSARC/2008/350 SMF Template Extensions, which permits more > extensive checking of manifests. You have correctly diagnosed the cause of > the message and that is the postrun.xml manifest does not have a stop > method. > Thanks for verifying that the postrun.xml manifest needs a stop method. I searched in bugster and don't find a bug about this. I will file a bug to track this. > Note that this is only a warning. Unless you use the -V option of svccfg > import or use svccfg in interactive mode, the manifest will still be > imported despite the warning. > Yes, I am aware that it is a warning. I can confirm that the manifest actually got imported. I was concerned because I didn't see the same warning on my b105 system. I wanted to make sure that there's not some subtle thing that I missed. > The extended templates project was putback into build 102. So the > interesting question is why you are not seeing the warning on your 105 > system. If I natively run "svccfg validate > /var/svc/manifest/system/postrun.xml" on my snv_105 system I do see the > message. If I can login to your 105 system, I'd be happy to look at your > setup. > > If I run "svccfg validate /var/svc/manifest/system/postrun.xml" on my snv_105 system, I do see the warning too. However, if I run the commands the way I reported, I don't see the warning. I had to run the commands the way I did because we are trying to not place the restriction on people to have to upgrade their system to b105 to use our tool.
I will send you info about my system in a private email. Thanks, --Karen
