On Fri, Mar 05, 2004 at 11:34:16AM +0100,
Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote
a message of 26 lines which said:
> I use Mon::Client and mod_perl to serve information from mon on the
> Web. At the command line, everything is fine, but when running under
> mod_perl (either Mason or Apac
On Fri, Mar 05, 2004 at 07:58:52AM -0500,
David Nolan <[EMAIL PROTECTED]> wrote
a message of 43 lines which said:
> Are any of your monitor scripts returning particularly large
> summary/detail messages?
We typically have 300 watches, each with two tests.
> In particular, Mon 0.99.2 uses Text
--On Friday, March 05, 2004 11:34 AM +0100 Stephane Bortzmeyer
<[EMAIL PROTECTED]> wrote:
I use Mon::Client and mod_perl to serve information from mon on the
Web. At the command line, everything is fine, but when running under
mod_perl (either Mason or Apache::Registry), I experience the infamo
I use Mon::Client and mod_perl to serve information from mon on the
Web. At the command line, everything is fine, but when running under
mod_perl (either Mason or Apache::Registry), I experience the infamous
"Segmentation fault" when calling things like list_opstatus. Other mon
commands work.
Is t
