David Bustos writes: > Quoth Tom Whitten on Thu, Feb 28, 2008 at 01:57:46PM -0700: > > When I went to the code for engine_import() at > > http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/cmd/svc/svccfg/svccfg_engine.c#506, > > I discovered that the code already has provision for a -V option. See > > lines 535-546. Then if you go down to lines 605-607, you see that the > > import -V option has not been implemented. > > > > So I have a couple of questions for the orignal SMF team. What was the > > intent for the -V option? Is there any reason why I should not go ahead > > and use it to indicate strict template validation checking? > > It was ARC'ed in PSARC 2004/524 with > > The -V option to the import subcommand provides a verified import > capability, in which the manifest contents are compared to the > final repository contents. A non-zero exit status is returned in > the case of a difference. (As override attributes are required > for a manifest to override a pre-existing definition in the > repository, the -V option is provided to verify exact manifest > installation.) > > See also greenline bug 1000628. This was probably largely obsoleted by > my last-import stuff. I don't see why you can't change the meaning. > > > David
Thanks for the history, David. I'll go ahead and change the meaning of -V as you suggest. tom
