I noticed one of my best ships, celery MkII-880, had an unusual low keyrate on the proxy.
Did a pslist (from sysinternals pstools) and what do I see ?
Name Pid - Pri - Thd - Hnd - Mem - User Time - Kernel Time - Elapsed Time
---
dnetc 508 - 4 - 6 - 109 - 3344 - 63:23:20.366 - 0:00:11.776 - 92:41:27.739
---
explorer 904 - 8 - 15 - 471 - 5616 - 0:00:17.284 - 0:01:09.750 - 29:33:42.697
AlogServ 980 - 8 - 2 - 20 - 904 - 15:15:28.813 - 13:51:08.877 - 29:34:12.042
While the system had been running for 92 hrs, dnet had only got 63 hrs of cpu, while a process called alogserv stole 15 hrs in the last 29 hrs. Coincidence, explorer had restarted also 29 hrs ago...
Looks like an app error has been handled badly, and the workstation needed a reboot.
The user had not noticed anything. So tell your net/sysadmins that dnet allows to detect and fix problems before the end user even gets a chance to complain 😀 !
Did a pslist (from sysinternals pstools) and what do I see ?
Name Pid - Pri - Thd - Hnd - Mem - User Time - Kernel Time - Elapsed Time
---
dnetc 508 - 4 - 6 - 109 - 3344 - 63:23:20.366 - 0:00:11.776 - 92:41:27.739
---
explorer 904 - 8 - 15 - 471 - 5616 - 0:00:17.284 - 0:01:09.750 - 29:33:42.697
AlogServ 980 - 8 - 2 - 20 - 904 - 15:15:28.813 - 13:51:08.877 - 29:34:12.042
While the system had been running for 92 hrs, dnet had only got 63 hrs of cpu, while a process called alogserv stole 15 hrs in the last 29 hrs. Coincidence, explorer had restarted also 29 hrs ago...
Looks like an app error has been handled badly, and the workstation needed a reboot.
The user had not noticed anything. So tell your net/sysadmins that dnet allows to detect and fix problems before the end user even gets a chance to complain 😀 !
