Upstart support for Zabbix services
Bug #1047837 reported by
Christian Kampka
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zabbix |
New
|
Undecided
|
Unassigned | ||
zabbix (Debian) |
Fix Released
|
Unknown
|
|||
zabbix (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
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.
Related branches
lp:~kampka/ubuntu/quantal/zabbix/upstart-support
- Dimitri John Ledkov: Approve
- James Page: Approve
- Ubuntu branches: Pending requested
-
Diff: 238 lines (+150/-0)11 files modifieddebian/changelog (+7/-0)
debian/zabbix-agent.default (+8/-0)
debian/zabbix-agent.upstart (+41/-0)
debian/zabbix-proxy-.upstart (+41/-0)
debian/zabbix-proxy-mysql.zabbix-proxy.default (+2/-0)
debian/zabbix-proxy-pgsql.zabbix-proxy.default (+2/-0)
debian/zabbix-proxy-sqlite3.zabbix-proxy.default (+2/-0)
debian/zabbix-server-.upstart (+41/-0)
debian/zabbix-server-mysql.zabbix-server.default (+2/-0)
debian/zabbix-server-pgsql.zabbix-server.default (+2/-0)
debian/zabbix-server-sqlite3.zabbix-server.default (+2/-0)
description: | updated |
Changed in zabbix: | |
status: | Unknown → New |
Changed in zabbix: | |
status: | New → Won't Fix |
Changed in zabbix (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
summary: |
- Upstart support + Upstart support for Zabbix services |
Changed in zabbix (Debian): | |
status: | Unknown → Won't Fix |
Changed in zabbix (Debian): | |
status: | Won't Fix → Fix Released |
To post a comment you must log in.
These Upstart job configuration files look very good. Just a couple of points:
- are the following files required? Do they apply where no default database has been configured? Or are they an oversight?
zabbix- proxy-. upstart server- .upstart
zabbix-
- Since all the .upstart files share the same pre-start, as an optimisation, you could potentially create a "zabbix-setup" job that does that setup and have it 'start on (filesystem and net-device up IFACE=lo)' and 'export DIR' such that the remaining Upstart jobs could simply 'start on started zabbix-setup'.