Is there a problem with running
# service --status-all
as root over ssh?
A system that I performed this command upon has become non-responsive on all ports, leading me to conclude that it is either hung or the cpu is completely consumed with some task.
Regards,
Output to point of failure:
... Active Mount Points: -------------------- hcid is stopped sdpd is stopped hidd is stopped cpuspeed is stopped crond (pid 3334) is running... cupsd (pid 3806) is running... cups-config-daemon (pid 3404) is running... dc_client is stopped dc_server is stopped dhcpd is stopped Device not specified in /etc/sysconfig/diskdump Usage: /etc/init.d/dkms_autoinstaller {start|stop}
James B. Byrne wrote:
Is there a problem with running
# service --status-all
as root over ssh?
A system that I performed this command upon has become non-responsive on all ports, leading me to conclude that it is either hung or the cpu is completely consumed with some task.
Regards,
Output to point of failure:
... Active Mount Points:
hcid is stopped sdpd is stopped hidd is stopped cpuspeed is stopped crond (pid 3334) is running... cupsd (pid 3806) is running... cups-config-daemon (pid 3404) is running... dc_client is stopped dc_server is stopped dhcpd is stopped Device not specified in /etc/sysconfig/diskdump Usage: /etc/init.d/dkms_autoinstaller {start|stop}
sounds like some service in /etc/init.d crashed when it was invoked with `status` as the argument. dkms_autoinstaller simply didn't support status, so it returned that error.