I've reconfigured nagios to run as the same user and group as that of the
web server. Still getting this command file issue.
Any other suggestions?
Many thanks...
On Sun, Oct 3, 2010 at 1:25 PM, Ilan Berkner <[email protected]> wrote:
> Yep, there's no question that's what it is, but I've set it up so that the
> webserver user is part of the group that owns the rw directory with the
> sticky bit set, but no luck (yet)
>
>
> On Sun, Oct 3, 2010 at 10:37 AM, Marc Powell <[email protected]> wrote:
>
>>
>> On Oct 3, 2010, at 8:48 AM, Ilan Berkner wrote:
>>
>> > Did not work, probably b/c I'm restarting the service as root?
>> >
>> > Is there a way to tell under which user nagios is trying to access the
>> nagios.cmd file?
>>
>> Your web server is trying to write to the pipe so it's whatever user your
>> web server is configured to run as.
>>
>> --
>> Marc
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Nagios-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/nagios-users
>> ::: Please include Nagios version, plugin version (-v) and OS when
>> reporting any issue.
>> ::: Messages without supporting info will risk being sent to /dev/null
>>
>
>
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
