>If the permissions on /bin/ping were incorrect, it may mean that
>your system has been cracked. You probably should check by
>running ``rpm -V iputils'' which will show changes in any files
>in the package.
Thanks Bill for your concern and tips, but it is me who accidentally change the
file per
On Thu, Dec 18, 2008, Jun Salen wrote:
>>From what I can see nagios' check_ping monitor executes /bin/ping,
>>in which case you need to make sure /bin/ping is owned by root
>>and is setuid (chmod u+s /bin/ping)
>>
>>nate
>That solved it. Same with file permission with mount, umount, su, and
>ping6
>From what I can see nagios' check_ping monitor executes /bin/ping,
>in which case you need to make sure /bin/ping is owned by root
>and is setuid (chmod u+s /bin/ping)
>
>nate
That solved it. Same with file permission with mount, umount, su, and ping6.
Thank you very much.
Get your new E
Jun Salen wrote:
> Hi,
>
> The Ping service in Nagios has "unknown" status which was previously OK,
> this happens after i messed up some of the files owner and accidentally
> change it to Apache. Although I restored most of the file permission back to
> Root, the problem above still appears which
Hi,
The Ping service in Nagios has "unknown" status which was previously OK, this
happens after i messed up some of the files owner and accidentally change it to
Apache. Although I restored most of the file permission back to Root, the
problem above still appears which I suspect is due to permi
5 matches
Mail list logo
