Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I use Zeus zxtm's SOAP API. IIRC, when I look at the wrong place I get documentation like "this is a char[]". The SOAP API documentation does actually get around to naming what the available keys are. Thus far I've never actually had to resort to reverse engineering because the entire API really did seem to be documented (if lightly fragmented).

    I'm using using WSDLs from Rake in Ruby. Works fine.

  • Yeah, I did it.

    At least all the bad bits (in the embedded stuff released with Netsaint 6.x Nag 1 - 3.x.

    A local .Au guy solved a problem (of wasting a copy after a fork) for Perl plugins. I think he did a good thing.

    Unfortunately, I couldn't (and still can't) see how to preserve the existing REPL semantics (ie schedule a plugin, fork, exec the plugin and return whatever exec() returns to Nagios) and not re-eval the Perl plugin each time its scheduled.

    Also, I was too stupid to think that with no adequat

    • I'm sorry, you did what now? You wrote the logic that sucks plug-in code into Nagios? I'm confused.

      REPL means something other than "schedule a plugin, fork, exec the plugin, ..."... REPL means read, eval, parse, loop. That's the style of environment provided by old BASIC interpreters that accepted a command, ran it, and printed the output. Forth and a number of other systems are famous for it, and Python does that too (as a default when run without other arguments).

      Did I say that many people should shut