Zhenghui Xie wrote: > Dave Miner ?????????: > >>> Below is the table of services that have dependencies on these obsoleted >>> services: >>> >>> service name state in standalone profile >>> ------------------------------------------------------------------- >> ... >> >>> network/inetd:default disable >>> >> I see no reason why inetd should be disabled by default in a >> standalone or any other profile that Solaris provides by default; its >> only function is as a listener/restarter for other services, each of >> which can be enabled/disabled directly. The only thing that disabling >> it will do is make the first inetd-restarted service which is needed >> not run until the administrator also enables inetd, which is clearly >> an undesirable two-step. >> > If the network environment changes, do we need to restart or refresh > inetd? For instance, if system switch from standalone to > network-connected, will inetd-related configuration change? If not, I > agree that we should enable inetd at standalone as well. >
If there's a problem with that case (and I don't see why there would be since inetd generally works just fine with current profile switchers such as netprof, inetmenu, or the NWAM prototype), the solution is not to disable inetd, but to characterize the problem and fix inetd so that it deals with such a transition properly. Dave
