On 04/02/16 19:40, Marko Myllynen wrote:
Hi,
Related to the recent discussions around pmcd(1) and zbxpcp(3) [1,2] I
checked the init script files provided by PCP:
# grep chkconfig: /etc/init.d/pm* | sort
/etc/init.d/pmcd:# chkconfig: - 95 05
/etc/init.d/pmie:# chkconfig: - 95 05
/etc/init.d/pmlogger:# chkconfig: - 95 05
/etc/init.d/pmmgr:# chkconfig: - 95 05
/etc/init.d/pmproxy:# chkconfig: - 95 05
/etc/init.d/pmwebd:# chkconfig: - 95 05
Wouldn't it be better to prioritize pmcd first and then start the rest
(prioritizing them as needed as well)?
For a daemon like pmcd(1) used by many other services 95 is perhaps a
bit late although I realize that some PMDAs might have dependencies to
other services. But I wonder would something like 85 still be possible
as pmcd(1) startup priority? (Zabbix Agent is started at 86.)
1) http://oss.sgi.com/pipermail/pcp/2016-January/009403.html
2) http://oss.sgi.com/pipermail/pcp/2016-January/009410.html
Thanks,
I think 95 is an (almost) arbitrary number plucked from "the pool of
ignorance".
With so many init-like schemes in play now, I'm not sure it is possible
to arrive at a "correct" choice everywhere and indeed the chkconfig:
line is irrelevant on lots of platforms.
And there is one *added* confusion here, namely that things like pmie
and pmlogger (and possibly pmmgr) _could_ be launching a mix of PMAPI
clients that are fetching from local or remote pmcd instances, and for
the remote ones, it matters not a toss when then local pmcd is started,
nor if it is started at all!
|