<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">I guess the root privileges are dropped after reading the config files. So for an startup as root nagios can access the file.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The reload just sends a HUP Signal to the process now running as nagios user. So it won't work.</DIV></BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV>Thanks, Hendrik -- yes, that is what I was thinking, too. I assume this is a change from the 2.x branch, in which case it might be wise to have nagios 3.x read resources.cfg only after dropping its root privileges to explicitly force people to correct this. (I.e., prevent nagios from running at all as opposed to potentially running for a long time and then acting weird.)<DIV><BR class="khtml-block-placeholder"></DIV><DIV>best,</DIV><DIV>Jeff</DIV><DIV><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "></SPAN><DIV><BLOCKQUOTE type="cite"></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>