> that was way out of context for my mind - which location is set where
> (examples)?
Yeah, I should have started a new thread, sorry Michael.
> on rhel, the cmdpipe location is set to
> %{_localstatedir}/spool/icinga/cmd/icinga.cmd in both packages. maybe
> you've got a config leftover at your installation.
In the rebuilt rpm from git,
/etc/icinga/icinga.cfg
command_file=/var/icinga/cmd/icinga.cmd
yet the spec is as you defined, however I see this in my pull:
%define extcmdfile %{_localstatedir}/spool/icinga/cmd/icinga.cmd
%define extcmdfiledir %{_localstatedir}/icinga/cmd
Looks like extcmdfiledir is incomplete.
>From packages built from the release tar for icinga-web:
<resource name="icinga_pipe">/var/spool/icinga/cmd/icinga.cmd</resource>
Just a WAG but I forgot about /etc/icinga-web/conf.d/access.xml
and it looks like when I made the values consistent with the erroneous
value in the cfg from the icinga git pull, it was overridden by the conf.d
files. It's all good now.
Much appreciated,
jlc
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
