limits for one check would be set 2 times higher than for //Update interval// 1 second. * Startup and shutdown scripts for Java gateway no longer hide error messages on startup. They now also detect stale PID scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 5.3 Configuring

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 3 Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

limits for one check would be set 2 times higher than for //Update interval// 1 second. * Startup and shutdown scripts for Java gateway no longer hide error messages on startup. They now also detect stale PID scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 5.3 Configuring

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 3 Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 3 Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Supported platforms Due to the security Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. 3 Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh 34 Note that unlike server or proxy, Java gateway is lightweight and does not

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need

scripts The scripts are used to automatically start/stop Zabbix processes during system’s start-up/shutdown. The scripts are located under directory misc/init.d. Server process types • alert manager - Configuration files for Logback. shutdown.sh startup.sh Convenience scripts for starting and stopping Java gateway. settings.sh Configuration file that is sourced by startup and shutdown scripts above. Configuring script: $ ./startup.sh Likewise, once you no longer need Java gateway, run the shutdown script to stop it: $ ./shutdown.sh Note that unlike server or proxy, Java gateway is lightweight and does not need