Ton, Thanks for the note. I totally understand the ps issue. A few jobs ago, I was in an entirely Solaris environment, and it took me about 6 months before it got natural for me to run 'ps -ef' vs 'ps ax' (or the older 'ps -ax'). Then, when I left that job and returned to a Linux environment, I kept banging 'ps -ef' for months.
Joe On May 6, 2009, at 12:46 AM, Ton Voon wrote: > Just to let you know that the imminent Opsview 3.0.4 will have that > service check re-written using check_tcp instead of check_procs. The > reason we have this problem is that we tried to use a check_procs > which is consistent across different platforms, but it turns out > that due to underlying ps differences, it is not possible to get a > single check_procs command to give the same results on all systems. > > So we've changed the approach to use check_tcp against the command > pipe that opsviewd uses instead, which more accurately reflects the > availability of the opsviewd process. > > If you upgrade your systems, you'll need to manually change your > existing Opsview Daemon service check (because our upgrades do not > touch existing service check definitions), but this will be > documented for the release. > > _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
