The process checking is use a different way to check then the service, infact they could not use the same technique as from a API point of view checking a process or sevice is totaly different. What does take time and that is something "generic" of the OS, that is authentication and there is no way around it. dirk
-------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Goggins, Patrick Sent: Thursday, April 16, 2015 8:30 PM To: Servers Alive Discussion List Subject: [SA-list] Windows Service Checking Historically weââ¬â¢ve used the NTService check for monitoring windows services that could not respond on a given port. However as there was a third-party library involved, it was less than responsive to the timeout parameter and at times run upwards of 20-seconds per check. Does the NTProcess check use the same library and is it bound to the same restrictions? Thanks, ~Patrick To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
