If the zabbix server is terminated before being able to connect to the database, it will not destroy the shared memory segments and semaphores properly, leaving them allocated in the OS.
- Start the zabbix server with incorrect database parameters, so it will wait on startup
- Check with the ipcs command the allocated shared memory segments and semaphores:
- Stop the zabbix server using either kill or pkill and sending SIGTERM:
- Run ipcs again.
- The memory segments and semaphores will still be there.
2.2, 3.0 and 3.2 leak both shared memory and semaphores. Trunk, after
ZBXNEXT-3687 went in, leak only one semaphore