search for: check_ps

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>

>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 Email address! Grab the Email name you&#39;ve always wanted before someone else

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 permission. Does anybody have idea where to look at. Thanks, junji aisalen.wordpress.com Linux

On CentOS 4.5, I have Cacti and Nagios installed. I'm trying to "glue" them together with a program called n2rdd but am having a problem that I wondering is Perl-related. When I run "tail /var/log/nagios/rra/n2rrd.log", I see lots of this sort of thing: server01: Missing template for "server01" service "check_ping"

...and thus allow the chekcing of pids, without sending any signal. This scanning is a lot will get people that hack the kernel code that generates /proc entries to leave their evil processes out. Kudos for the idea are due to Solar Designer. Once enbaled you can select killing scanning by feeding check_ps -p or - --killscan on the argument list. Please be aware that kill scanning, and check-ps in general, is still experimental. Assuming you want to receive reports via email when using the email option please change cfg_email.h; at present the reports get sent to dps@io.stargate.co.uk, which is...

It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is this prohibition on "name" really the desired behaviour?

Nagios support "custom object variables" (http://nagios.sourceforge.net/docs/nagioscore/3/en/customobjectvars.html) buy prefixing them with an underscore: define host{ host_name linuxserver _mac_address 00:06:5B:A6:AD:AA _rack_number R32 } However, I can''t determine how to use these with puppet nagios resources. I''m assuming they aren''t supported, but

The Wine development release 4.16 is now available. What's new in this release (see below for details): - More reliable mouse grabbing in games. - Better cross-compilation support in WineGCC. - Improved compatibility with Windows debuggers. - Various bug fixes. The source is available from the following locations: https://dl.winehq.org/wine/source/4.x/wine-4.16.tar.xz

The Wine development release 3.9 is now available. What's new in this release (see below for details): - OpenGL core contexts enabled by default in Direct 3D. - Beginnings of Direct 3D 12 implementation using vkd3d. - More support for the Task Scheduler. - Some more Task Dialog support. - Better arrow support in GdiPlus. - Various bug fixes. The source is available from the

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my