On Sun, 2010-08-22 at 18:39 -0700, JD wrote: > On 08/22/2010 01:38 PM, Robert G. (Doc) Savage wrote: > > JD, > > > > It's possible that system-config-services is not working correctly. As > > an alternative, use chkconfig to look at the default startup status for > > each of those services: > > # chkconfig --list | grep akmods > > akmods 0:off 1:off 2:on 3:on 4:on 5:on 6:off > $ chkconfig --list | grep akmods > akmods 0:off 1:off 2:off 3:off 4:off 5:off > 6:off > > ditto with the rest: capi hsqldb isdn jetty lm_sensors racoon sandbox > vmware zvbid > > So, I still cannot explain this. > > For example, capi is reported by system-config-services as running, > BUT: > > $ sudo service capi status > capi not installed - Connection timed out (110) > > So, how could it be reported as running. > > akmod is also reported as running and ther is not S*akmods in any of > /etc/rc[0123455].d > > also, hsqldb is disabled, yet it is reported as running, > same as isdn, jetty, lm_sensors, racoon, sandbox, vmware, zvbid > > In summary, system-config-services cannot be relied on to correctly > report what services are running or, disabled, or stopped. A service can be disabled (i.e. not enabled) in a run level, yet have been started by something else, perhaps inadvertently. Before declaring s-c-s to be buggy, it would be important to discover if these things actually *are* running or not, using ps, and if so what their parent processes are. poc -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
