in reply to Anticipation of future needs and other musings from the crystal ball

I'd order it as below, but it is a matter of taste. I think it secure enough - it won't do anything the user himself can't do.

PROCESS = ... MESSAGE = ... ALERT = ... PROCESS = ... MESSAGE = ... ALERT = ...

I got here at July 12th, 2002 :)

  • Comment on Re: Anticipation of future needs and other musings from the crystal ball
  • Download Code

Replies are listed 'Best First'.
Re: Re: Anticipation of future needs and other musings from the crystal ball
by Limbic~Region (Chancellor) on Sep 03, 2002 at 23:44 UTC
    My actual config file looks a tad bit different, and I agree with you. I was just trying to give an example and I forgot to include what it would take to add a new check - that was my intention, so here it is:

    PROCESS = /sshd MESSAGE = The SSH Daemon has terminated ALERT = major

    In just a few key strokes, the program now performs one more check and no one even had to open up the code. Of course, I realize that if you want to define a new "type" of check that it has to be coded. One of the other side effects of doing this is having multiple configuration files. Instead of hard coding to "default.ini" - you could use getargs to specify an alternate - as in changing disk space threshold. Each admin could tailor the file to their liking.