Quoth Steven Sim on Thu, Jun 22, 2006 at 01:57:20PM +0800: > In order to do what you suggest, it would require me to delete the > service in the current active repository, modify the said service > manifest in /var/svc/manifest and subsequently reimport them using svccfg.
Deleting the service is not strictly necessary, since svccfg will upgrade the repository correctly. > Forgive me, but I had thought modifying manifest definition in > /var/svc/manifest was NOT recommended nor supported and that Sun > recommended all modification to the current repository through the > standard svccfg interface. Indeed, it is not recommended; I didn't realize this was a Sun-delivered manifest. Try this: svccfg -f - <<END select application/management/sunmcwebserver setprop start/group = astring: root setprop start/limit_privileges = astring: :default setprop start/privileges = astring: :default setprop start/project = astring: group.sunmc setprop start/resource_pool = astring: :default setprop start/supp_groups = astring: :default setprop start/use_profile = boolean: false setprop start/user = astring: root setprop start/working_directory = astring: :default END > I have found a thread started by Mark Scheufele that ended with the > following; > > "thanks to David Bustos who pointed me to bugID 5093847 and who also > provided a workaround I am now able run samba under a specific project > context. According to this bug it is necessary to put either a > method_credential or method_profile element into the method_context > section. I had to delete my current samba manifest and add the > method_credential into the xml file and import again. After that the > processes were assigned to the defined project." > > I also unable to locate BugID 5093847 via Sun Solve even though I have a > platinum account. Could anyone help? http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=5093847 Please ask Sun Support to add a call record for you. David
