plans for system-config-services, was: early-gdm redux

[Nils Philippsen]

On Thu, 2007-09-13 at 19:06 -0400, Jon Nettleton wrote:

> I can think of two approaches.
> 
> a)  Do this in system-config-services.  Checking NetworkManager and
> Dispatcher on makes the Network-Services tab active and disables
> "known services" from the init list and enables them in the
> Network-Services list.  Disabling these does the reverse of course.
> 
> b)  Only have these services in the Network-Services tab or run-level
> N for chkconfig and extend /etc/init.d/network to run through the
> /etc/NetworkManager/dispatcher.d/ directory and run the S* services.
> This message is a little off because it basically puts partial init
> functionality in the network script.  The code should be trivial
> though.

Don't get too attached to tabs in system-config-services. My plan is to
get rid of them altogether and have all services (SysVinit-, xinetd- and
eventually network-based or (more generically) on-demand services) in
one list. Each entry in this list would consist of the service name, its
enabled/disabled and running/not running status. Now selecting an entry
would finally show the gory details: type of service, in which runlevels
it is enabled/disabled in case of a SysVinit service, etc.

Now what I really don't want to do is deal with service type transitions
(NMD gets stopped -> network-based services get normal SysVinit services
again) as I don't see real value behind it. If network-based services
need a daemon to run properly then it better ran. It's not really a new
situation -- if xinetd doesn't run, xinetd-based services don't get
started. Just as with every other basic building block of the system.

Makes sense?

Nils
-- 
     Nils Philippsen    /    Red Hat    /    nphilipp at redhat.com
"Those who would give up Essential Liberty to purchase a little Temporary
 Safety, deserve neither Liberty nor Safety."  --  B. Franklin, 1759
 PGP fingerprint:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011