From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724
Description of problem:
The service config application would be much more useful if it showed the
services current status.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Open Service configuration
2a.Try and find out the current status of a service, OR
2b. Start a service. Wait for feedback.
Actual Results: There should be status information for services. It should be
updated when that service is started or stopped or restarted.
I am not sure this is possible. A service is not necessarily running. The name
of the service does not correspond to the name of daemons that are running. For
instance the nfs service starts multiple nfsd's. A service is something that
starts at different runlevels. Maybe a tool like redhat-config-processes might be
closer to what you want.
Thanks for your reply.
> Maybe a tool like redhat-config-processes might be closer to what you want.
I'd really like to automate the `Open Services, check state on command line'
cycle. In fact, I probably don't think that cycle would happen - most users
would probably do everything from the command line simply (even if they
preferred a graphical app) because services can't tell them all the things the
`service' command does.
I'm really looking for something that provides the equivalent of the status
parameter in Services. I see as possible to implement and suitable for the
services app (will explain why in a sec) ang I think it will give users the
feedback they expect when starting or stopping services - they're already
using `service (service) status' for this, it seems sensible to put somethign
similar in the app.
> For instance the nfs service starts multiple nfsd's.
Indeed - and ldap starts both slapd and slurpd, etc. The way I see things that
sholdn't be a problem. Each application would have a definition of what
constitutes a sane running state. The Linux Standards Base allows Red Hat to
put this information in the initscript if we wish (there's already similar
information there), or somewhere else may be more appropriate. For example:
nfs: at least one instance of rpc.mountd, and at least one of nfsd.
ldap: at least one slapd and slurpd
In Services, each application can be in one of the following states:
green - the system is in its sane state
dark green - for application like Kudzu and Netfs - services which are not
deamons. As you mentioned, a service is not necessarily running - this lets
users know that these services are OK.
yellow - the system is not in its sane state
red - the service is not running, lockfile removed, etc.
Users can click/hover on a service's state to get more info - basically the
same stuff that you get with the sstatus parameter, telling you exactly what
processes are running.
Thanks for your I hope that's addressed your concern, and I hope you don't
mind me reopening the bug.
Erk, sorry about the duplicate.
I will make some changes to serviceconf to reflect the status after the next
release of redhat. It is too late to get changes into milan. Good ideas though.
Fixed in redhat-config-services-0.8.3-1.
This will be in rawhide soon.