David Bustos wrote: > Quoth Riny Qian on Tue, Aug 01, 2006 at 02:07:09PM +0800: > >>#> svccfg -s test-fmri:porta setprop data/port="/dev/porta" >>svccfg: No such property group "data". > > > This is because your manifest has the data property_group element inside > the service element, not the instance element. Therefore svccfg import > created the property group on the service. This command tries to set > the property in the property group on the instance (test-fmri:porta), > but the property group doesn't exist. > > svccfg -s test-fmri setprop data/port="/dev/porta" > > or > > svccfg -s test-fmri:porta addpg data application > svccfg -s test-fmri:porta setprop data/port="/dev/porta" > > should work. >
Thanks for your clarification. BTW, type should also be specified since it is a newly-added property. :-) > >>#> svccfg -s test-fmri add portc >>#> svccfg -s test-fmri:portc setprop data/port="/dev/portc" >>svccfg: No such property group "data". >> >>What's wrong here? > > > When you create an instance, it doesn't have any property groups. You > must add the property group before you can set any properties in it. > > >>It seems that the listprop/setprop subcommands of svccfg does not >>support the composed property? > > > Indeed, svccfg doesn't know anything about property composition, but > svcprop uses composition by default. This is because svccfg is meant to > provide access to the bare metal of the repository, but unfortunately > right now it is also the only supported way to set properties. > I got it. It would be a very useful RFE to make svccfg be aware of the property inheritance/composition too and change the composed property to its own once a composed property is updated by setprop. thanks, Riny
