lianep at eng.sun.com wrote: > >>For example, I sometimes want to run more than one sshd, with >>different sets of interfaces and ports bound, and different >>configuration files specified for each. (For example, one bound on an >>internal RFC 1918 address and another bound on an external Internet- >>facing address.) >> >>There's no "competition," because they're intentionally configured >>differently. >> >>The only way I've found to do it so far is by setting up my own rc*.d >>scripts. > > > That seems to be because ssh doesn't offer you a way in the service to > specify the config file. If it did, you could do: > > svccfg -s network/ssh add myinst > svccfg -s ssh:myinst setprop ... (new configfile) > svcadm enable ssh:myinst >
I tried a service (manifest) using the inheritance, but found that the inherited property cannot be specified by svccfg though svcprop does show it in the property list. The test service is attached. #> svcprop test-fmri:porta | grep data/port data/port astring /dev/%i (here token is only effective in method! Is it possible to add the support into property?) #> svccfg -s test-fmri:porta setprop data/port="/dev/porta" svccfg: No such property group "data". #> 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? I also want to make adding another instance easier by just invoking "svccfg -s test-fmri add portx" and passing %i (instance name) into the svc method, thus users don't even need to set the port property. #> svcprop test-fmri:portc | grep start/exec start/exec astring /lib/svc/method/test-fmri\ %i BTW, I'm running snv_37. thanks, Riny -------------- next part -------------- A non-text attachment was scrubbed... Name: test-fmri.xml Type: text/xml Size: 967 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20060801/7e8764c5/attachment.xml>
