[dev.icinga.com #1416] icinga.passwd in wrong location

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/1416

Created by Wolfgang on 2011-04-19 17:45:06 +00:00

Assignee: (none)
Status: Rejected (closed on 2011-04-27 16:45:44 +00:00)
Target Version: (none)
Last Update: 2011-04-27 16:45:44 +00:00 (in Redmine)

---

Moving icinga.passwd into the Apache config dir seems to be the wrong location because the password file is NOT a file containing Apache config statements. Please choose another location (see http://www.nagios-portal.org/wbb/index.php?page=Thread&threadID=22463 for details).

[icinga-migration]

Updated by Meier on 2011-04-19 18:55:06 +00:00

Got any proposal where to put it instead?
For fedora/redhat/centos this is totally ok as the main config does "Include conf.d/*.conf" so there is no issue.
The previous location "sysconfdir/htpasswd.users" is not acceptable to me. Anyway this is only a sample config. Packagers will ship a working default config no matter what the sample-config is.

Foromer? Any comments on this?

[icinga-migration]

Updated by Wolfgang on 2011-04-19 20:31:50 +00:00

I guess it's not just "only a sample config". AFAIK it is used to create a file which is copied into the Apache config directory using "make install-webconf" and the place and creation of the authorisation file is described in the documentation.

SLES has a similar mechanism (Include .../conf.d/*.conf) so it might be an idea to propose the same for Ubuntu and describe that procedure in the documentation.

[icinga-migration]

Updated by mfriedrich on 2011-04-19 21:16:24 +00:00

cool.

another compatibility breaking fix which got lost in git history.

i've reverted the change in git master (yes i'm on holiday, but it's annoying to read about users complaining).

policy for future commits/merges like that - only if tested by at least 3 people. ask the dedicated sub project maintainers if it's ok to use such.

@wolfgang
please test the git master and mention that to the user then.

@chris
for the discussion itsself - those locations are well known and historical grown. changes can happen only if they are compatible. if not, they still need to remain sed, subst, awk or whatever tool you prefer within the spec file for installing it the proper way on the specific os. debian and others will need the known default, and breaking things won't solve the initial problem itsself.

and for now - bye bye.

[icinga-migration]

Updated by berk on 2011-04-27 08:14:01 +00:00

• Target Version changed from 1.3 to 1.4

[icinga-migration]

Updated by mfriedrich on 2011-04-27 16:45:44 +00:00

• Category deleted Installation
• Status changed from Assigned to Rejected
• Assigned to deleted Meier
• Target Version deleted 1.4

reverted everything.