Hi Guys,
I've just come across a bug when using net.tcp.listen to see if a particular listener is active. The problem occurs where it is not bound to all local addresses but rather to a specific one.
The command being executed by the agent to see if something is listening on TCP port 4100 is
This then looking for a service installed to listen on only one interface will always return 0 which is not correct.
If the command was to be changed to
would alleviate this problem and would cover both situations. Perhaps a further capability to be considered would be to specify the IP address to look on with '*' as an option for all/any interfaces.
Now, I do realise (and I am considering it) that a short term work around would be to add UserParameters for each of the needed services.
Cheers,
Brian.
I've just come across a bug when using net.tcp.listen to see if a particular listener is active. The problem occurs where it is not bound to all local addresses but rather to a specific one.
The command being executed by the agent to see if something is listening on TCP port 4100 is
Code:
"netstat -an | grep '*.4100' | wc -l"
If the command was to be changed to
Code:
"netstat -an | grep '.4100 ' | grep LISTEN | wc -l"
Now, I do realise (and I am considering it) that a short term work around would be to add UserParameters for each of the needed services.
Cheers,
Brian.