Quoth Zhenghui Xie on Thu, Sep 21, 2006 at 04:43:32PM -0700: > >There may not be a compelling reason for this, but it seems possible > >that someone will want his service to run only when no network is > >available, but only start once NWAM has determined that. I think we > > I am not sure I get this part. You mean somebody wants his service to > run at no-network and don't start it when network available?
Yes, I think. > >could support that by separating a boot profile from the standalone > >profile. The boot profile would always be active at boot, and would > >presumably only enable enough services to bring NWAM up, and then NWAM > >would look for networks, and if it didn't find any, it would switch to > >the standalone profile. It's probably not worth setting the system up > >by default this way, but it seems that this setup should work if the > >administrator desires it. > > But basically, I think the issue should be solved by allowing users to > have their own customized standalone profile? ( Section III, > dependencies, second paragraph) Not as you have presented it. I think your plan is to have the standalone profile active on boot. Then any services which the user has enabled in that profile will be started as soon as their dependencies are met. If a user wants the service to only be started once NWAM has verified that no networks are available, then NWAM will have to switch from the initial profile to a different standalone for this to happen. > >Why should ssh be enabled when there is no network? I think in the vast > >majority of cases, without a network, it will be a waste of resources. > >Of course, if someone wants to run sshd without network connectivity, > >then he can customize the standalone profile. > >... > > I think the answer to this would be the same as "whether to enable inetd > or not". Or a more generic qustion is, should we enable those services > that can work properly at no network but without a network they don't > really anything? Since there are legitimate reasons to start them either way, both should be possible. The question here is what the default should be. Without knowledge of a user's specific intentions, the only difference is resource usage (e.g., memory & boot time). In most cases, the user won't need sshd running without network connectivity, so we should save him the resources by having it disabled by default. inetd is similar, but has the additional wrinkle of being a dependency for a lot of services. David
