[Nagiosplug-devel] Notification of plugins 1.4.14 release

[Kyle O'Donnell]

I've used this for SunOS 5.8 5.9 and 5.10

--with-ps-command="/usr/bin/ps -eo 's uid pid ppid vsz rss pcpu etime
comm args'" \
--with-ps-format="%s %d %d %d %d %d %f %s %s %n" \
--with-ps-cols=10 \
--with-ps-varlist="procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procetime,procprog,&pos"


On 4/28/09, Ton Voon <ton.voon at opsera.com> wrote:
>
> On 28 Apr 2009, at 16:23, Kyle O'Donnell wrote:
>
>> What is broken with check_procs on solaris?  I have found formulating
>> the ps command works better than using the native nagios-plugins
>> methods.  I can provide you with working compile options.
>
> This question comes up a lot so I've put a FAQ entry up:
> http://nagiosplugins.org/faq/compile/pst3
>
> I'm happy to update the entry with your compile options if you let me
> know what they are.
>
> I think the 64 bit issue is due to a Solaris system using Sun's cc
> rather than gcc. This is a good example of a tinderbox build server
> being helpful here: http://nagiosplugins.org/tinderbox. Anyone that
> can offer a Solaris server with Sun's cc will mean we can catch these
> issues earlier.
>
> My thoughts about check_procs is that I want to be able to run some
> tests with actual ps outputs from running systems. I need to spend
> some time on this.
>
> Ton
>
>
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations
> Conference from O'Reilly Media. Velocity features a full day of
> expert-led, hands-on workshops and two days of sessions from industry
> leaders in dedicated Performance & Operations tracks. Use code vel09scf
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________________
> Nagios Plugin Development Mailing List
> Nagiosplug-devel at lists.sourceforge.net
> Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>