Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #10739] Crash on startup with incorrect directory permissions #3723
This issue has been migrated from Redmine: https://dev.icinga.com/issues/10739
Created by pschoenfeld on 2015-11-27 13:48:43 +00:00
When installing from source (at least when installling with a custom INSTALL_PREFIX) the permissions of the files installed by make install are not correct.
Steps to reproduce:
In my test it failed due to /opt/icinga2/var/cache/icinga2/ not being owned by the icinga user. Chowning that directory makes icinga2 continue (until the next permission problem if any).
2015-12-08 14:12:13 +00:00 by mfriedrich 407a750
2015-12-08 14:28:51 +00:00 by mfriedrich 833e280
Updated by pschoenfeld on 2015-11-27 16:16:16 +00:00
There is no error message at all. In the case described above only one message is printed at all and what follows is a SIGABRT.
Updated by mfriedrich on 2015-11-27 17:57:01 +00:00
Well, that's what I'm taliking about. I do see that myself from time to time, but I don't care much as we generally support and promote package installations. The source installation got issues with setting proper permissions in the first place, there's a ticket somewhere to fix that. Low priority though.
Updated by pschoenfeld on 2015-11-28 10:48:50 +00:00
Uh. I think that's a fatal attitude. After all it's the software, which is obviously not handling environmental errors properly in the first place. What if permissions get screwed up in a real environment? What if a new such case is introduced and one of the package maintainers is missing that one? What if it were a similar problem but with more troublesome consequences?
So, while I agree that the buildsystem issues could be thought of as "low prio", I don't think that any issue in the software itself can be.