Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-3687

Rework semaphore and shared memory management to minimize conflicts with other applications and inbetween simultaneously running Zabbix daemons

XMLWordPrintable

    • Team C
    • Sprint 1, Sprint 2, Sprint 3, Sprint 4, Sprint 5
    • 16

      Idea is to abandon key usage. Neither generated with ftok() nor generated in any other way. Keys should not be used to create Zabbix mutexes and shared memory segments because explicit key usage may lead to conflicts when other applications depend on the same key. Alternative is to use IPC_PRIVATE constant and forget about ftok().

      As a side effect this change requires that we remove SQLite support for main Zabbix database because we will not be able to share mutex for DB access between frontend and server any more.

            Unassigned Unassigned
            glebs.ivanovskis Glebs Ivanovskis (Inactive)
            Team C
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: