Hi,
On 2016-01-27 18:37, Trey Dockendorf wrote:
>
> Wrt the solution for starting up the services in the right order, I was
> doing more or less the same as Trey (I had zabbix-agent chkconfig'ed off
> and started in /etc/rc.local). Perhaps one option would be adjusting
> priorities for these services so that pmcd(1) would be started first but
> I'm not sure how elegant that would be unless either upstream changes
> them. If there are no better suggestions, perhaps we could try asking
> the zabbix-agent maintainers for that.
>
> The use of rc.local will work just fine though having upstream make a
> priority change would help too.
For systemd systems we can actually solve this on the PCP side as well:
---
src/pmcd/pmcd.service.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/pmcd/pmcd.service.in b/src/pmcd/pmcd.service.in
index 8da7798..c371860 100644
--- a/src/pmcd/pmcd.service.in
+++ b/src/pmcd/pmcd.service.in
@@ -3,7 +3,8 @@ Description=Performance Metrics Collector Daemon
Documentation=man:pmcd(8)
Wants=avahi-daemon.service
After=local-fs.target network.target avahi-daemon.service
-
+Before=zabbix-agent.service
+
[Service]
Type=oneshot
ExecStart=@path@/pmcd start
Thanks,
--
Marko Myllynen
|