Quoth Mark Scheufele on Wed, Apr 05, 2006 at 07:17:30PM +0200: > I only was able to change :samba to samba within the service definition > svc:/network/samba and not for the :default instance. But this change > did not resolve the issue.
What happened when the services started? > When the default instance is select there is > no property group method_context. That is expected; if the instance does not specify a property, it will be inherited from the service. > Maybe I do not fully understand how to set values for specific instances > and how instances relate to services or something like that. Here is the > xml for the manifest I used. It looks like it should work. How do you know it doesn't? Quoth mark scheufele on Fri, Apr 07, 2006 at 04:57:03AM -0700: > I am still fighting with the task "running the samba services under > the samba project context". First I created the property group > "method_context" with type framwork and added the property project > with value samba. Those configurations were done for the whole service > svc:/network/samba. But svcadm disable fmri:samba and restarting samba > did not put the smbd and nmbd daemons into the correct project. svc.startd expects more properties in the method_context property group. In general, you should not create it yourself. You should let svccfg create it according to a manifest. > My next try was I deleted the method_context property group for the > whole service and recreated it for the default instance (see the > following svccfg output): > > svc:/network/samba:default> listprop ... > restarter_actions/restart integer > method_context framework > method_context/project astring samba Indeed, this method_context is missing properties. svc.startd probably wrote an error message into the service's log file. Check /var/svc/log/network-samba:default.log . > Yet this also did not solve my problem. As I understand the > smf_method(5) manpage one can either set the method_context pg for the > whole service or each specific instance. Both ways I have tried > without success. I also tried different property group types (method, > framework, method_context)for the group method_context with no success > either. Method context properties should work in the method's property group or a method_context property group. If it exists on the instance, then it will override any settings on the service. If it doesn't exist on the instances, then any properties on the service will be inherited. David
