As part of the extended templates project we are planning to add a -V option to the svccfg import subcommand. This would tell svccfg to do strict checking to validate that the manifest is in conformance with the extended templates specifications. The import will fail if the validation fails. Without the -V option validation failures do not cause the import to fail, but warnings will be issued. This is for backwards compatibility.
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? tom
