Summary: | net-analyzer/nagios - Directory permissions for /etc/nagios are wrong, apache can't start | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joseph <syscon780> |
Component: | [OLD] Server | Assignee: | Sysadmin Bugs <sysadmin> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | tomwij |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joseph
2012-11-23 05:01:36 UTC
An alternative fix is to let Apache start under the nagios user. Don't even suggest that. (In reply to comment #1) > An alternative fix is to let Apache start under the nagios user. Not a good idea :-/ Hell will break loose apache use flag to set the group owner to apache? or maybe setting other to read for the required files? I would be fine with a 755 on /etc/nagios and 750 on the files that contain passwords or generally private stuff, myself. My solution has been to use ACLs, tbh, so that's not very flexible. I believe this is fixed in the latest nagios-4.x ebuilds. Per the elog: * Note that your web server user requires read-only access to * /etc/nagios. * * To that end, we have changed the group of /etc/nagios * to that of your web server user. blah blah blah This works for me with the out-of-the-box nagios configuration, and /etc/nagios has mode 750, so I don't think I've given apache access to anything it shouldn't have access to (lighttpd is the same way). If you're using some other web server, it will tell you to fix it on your own. Please feel free to reopen if the issue is not fixed. |