Hello, Simon. On 15/10/14 01:17, Simon Walter wrote:
>> But I had to change the settings provided by the package on >> /etc/icinga-web/conf.d/access.xml: >> >> <!-- allowed to be written to --> >> <write> >> <files> >> <!-- DGB - 20141013 --> >> <!-- <resource >> name="icinga_pipe">/var/lib/icinga/rw/icinga.cmd</resource> --> >> <resource >> name="icinga_pipe">/var/run/icinga2/cmd/icinga2.cmd</resource> >> </files> >> </write> >> <!-- allowed to be executed --> >> >> >> Is it feasible have to make this change or may be a bug in the package? > I had to do similar adjustments with the configuration files provided by > the Debian packages. Perhaps they are all sorted out by now. I just > haven't upgraded them to avoid the breakage until the packages "mature" > so to speak. It's all very fresh you know. ;) Thanks for sharing your experience. Maybe it's good that Michael or anyone else of Icinga Development Team tells us about the state of this to know if we will not have to be aware of this change after doing an upgrade. Best regards, Daniel _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
