Zabbix Documentation 5.0

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

User Tools

Site Tools


manual:config:notifications:action:operation:remote_command

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
manual:config:notifications:action:operation:remote_command [2019/12/18 15:09]
martins-v EnableRemoteCommands is deprecated on agent
manual:config:notifications:action:operation:remote_command [2020/02/14 16:00] (current)
marinagen paragraph about remote command execution with timeout
Line 67: Line 67:
 <​note>​Zabbix agent should run on the remote host and accept incoming connections. Zabbix agent executes commands in background.</​note>​ <​note>​Zabbix agent should run on the remote host and accept incoming connections. Zabbix agent executes commands in background.</​note>​
  
-Remote commands on Zabbix agent are executed without timeout by the system.run[,​nowait] key and are not checked for execution results. On Zabbix server remote commands are executed with timeout as set in the TrapperTimeout parameter of zabbix_server.conf file and are [[manual/​appendix/​command_execution#​exit_code_checking|checked]] for execution results.+Remote commands on Zabbix agent are executed without timeout by the system.run[,​nowait] key and are not checked for execution results. On Zabbix server ​and Zabbix proxy, ​remote commands are executed with timeout as set in the TrapperTimeout parameter of zabbix_server.conf or zabbix_proxy.conf file and are [[manual/​appendix/​command_execution#​exit_code_checking|checked]] for execution results. 
 === Access permissions === === Access permissions ===