Tony Nguyen wrote: > Yes, we probably need to know how the service relates to other services > to give good guidance.
The particular service in question is a management agent. > Look at dependency as things(services and configuration files) needed > for your new service to run. So your service will need to have > dependency on networking milestone, at the minimum. milestone/name-services looks plausible. I hadn't noticed it. > Does it make sense for any other service to depend on your service? That > is, if your service fails, should the system still be operation(other > services can still run)? If any service requires that your new service > be online to be operation, then that service will need to have a > dependency on your service. Hope that helps. There are no services outside our organization that depend on our service. The key questions are - how should we ensure that networking is up? (Whatever "up" means.) We currently depend on milestone/multi-user-server, and that will work but I don't know if it's right. Depending on milestone/name-services might be better. - Should we say that milestone/multi-user-server depends on our service? >> Assume that it pretty much needs the full network stack working. >> >> Should our service depend on milestone/multi-user-server? >> Should milestone/multi-user-server depend on our service? >> >> If the answer is that m-u-s should depend on our service, what should >> our service depend on? Is there a convenient way to say "all that >> usual networking stuff", or should we look at the existing services >> and try to pick the right ones? >> _______________________________________________ >> smf-discuss mailing list >> smf-discuss at opensolaris.org >> > >
