-
Incident report
-
Resolution: Fixed
-
Trivial
-
None
-
None
It's not very obvious if not test it with zabbix_get and recent agent versions 2.4+, so would be useful to document.
Especially a details that the forked process will be terminated.
As an example debuglog of agent 2.4.7rc1 (revision 54982):
# time zabbix_get -s localhost -k sleep[55]
ZBX_NOTSUPPORTED: Timeout while executing a shell script.
real 0m3.005s
user 0m0.004s
sys 0m0.000s
3055:20151029:100154.734 listener #2 [processing request] 3055:20151029:100154.734 Requested [sleep[55]] 3055:20151029:100154.734 In zbx_popen() command:' sleep 55; echo 55' 3055:20151029:100154.735 End of zbx_popen():9 3058:20151029:100154.735 zbx_popen(): executing script ... 3055:20151029:100157.734 In zbx_waitpid() 3055:20151029:100157.734 zbx_waitpid() killed by signal 15 3055:20151029:100157.735 End of zbx_waitpid():3058 3055:20151029:100157.735 listener #2 [waiting for connection]
Here https://www.zabbix.com/documentation/2.4/manual/config/items/userparameters
For example we have such details documented for remote commands and that's useful, https://www.zabbix.com/documentation/2.4/manual/config/notifications/action/operation/remote_command