On Wednesday 16 January 2008 13:28:20 Linda Walsh wrote: > I'm looking at (and have been resisting the change) in xinet.conf two > different ways of doing its "configuration". > > The can be summed up (using neutral terms) as "Way-A (WA) and "Way-B" > (WB) and "Way-C". > > In WA, we have something like: > > <local WA setup for xinet> > <list of all xinet services specifying disabled or enabled> > <then list of all services in config file to specify params > for WA services> > > <WB:> > <local WB xetup for xinet> > <include <subdir> with separate files, specifying on/off > and config for each for each service> > > <WC:> > <local WB setup for xinet> > <list of all xinet services specifying disabled or enabled> > <include <subdir> with separate config options for each > service> [...snip...] > Without basing your opinion on what just "happens" to already be > in place (that's cheating! :-)), which of the 3 ways do people > prefer? All-in-one, split/service (23 extra files in my config), or > all-control-in-one file with params being split/service. > > Comments? > Preferences? > FWIW, I believe both WA and WB have been "done", but I don't know > if WC has been tried.
I prefer WB, but with the following difference: Instead of using "include <subdir>" with separate lines for each service, use "includedir <subdir>" in a single line, with separate files in <subdir> for each service. This way, 1) the /etc/xinetd.conf never needs to change unless a global config option changes, 2) a directory listing of <subdir> clearly shows the services that are configured, and 3) examining a single service option file shows only the configuration for that service. Enabling/disabling a service is simple--add or delete its config file in <subdir> and have xinetd reload its config. Jim -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
