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

Use a controlling socket instead of signals for controlling the zabbix subsystem

    Details

    • Type: Change Request
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Server (S)

      Description

      Actually, for controlling the zabbix server at run-time, zabbix use a signal subsystem that is linux specific (for example you can't control zabbix at runtime on other operating systems).
      Being zabbix also used outside of Linux (and I know a lot of cases for it), the proposal is to replace the signal-based control mechanism with a socket-based one. This will allow:

      • Safety, as signal handlers interrupt the normal flow of the program (in particular, zabbix is not completely safe on the syscall handling for this).
      • Flexibility: It will be possible to implement in a future complex controlling behaviors (like statistics on stdout regarding the server performances).
      • Portability: All the systems where zabbix compile support the standard sockets interfaces.

      My idea is to have a separated utility (named like "zabbixctl"), that take care of the communication with the server and whatnot and report to the user if required (numbers, if the operation was successful etc).

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              abs Andrea Biscuola (Inactive)
            • Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: