[Bug 1047837] Re: Upstart support for Zabbix services

[Christian Kampka]

I feel like using symlinks for the upstart files already resolved most of what you could remedy by having an additional zabbix-setup job. As things are now, it would mean pulling one line from the generic upstart file and creating a new job just for creating a runtime directory. There is no benefit for administrators either because the services files are renamed to a generic version when building the package so there is ever only one upstart file present when deployed.
To me, adding the additional job feels more like adding additional complexity rather than optimization.

If you feel passionate about this, I would be okay with adding the
additional setup job, but I can see little benefit in doing so.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1047837

Title:
  Upstart support for Zabbix services

Status in Zabbix:
  Won't Fix
Status in “zabbix” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu uses Upstart instead of SysVInit to run the init process.
  Attached debdiff includes upstart scripts that will allow Upstart to
  start/stop all zabbix daemon components. Installation of the scripts
  will happen automatically using Ubuntus Upstart debhelper scripts,
  Debian will simply ignore them.

  The patch was also sent upstream to the Debian maintainers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zabbix/+bug/1047837/+subscriptions