Re^2: CGI "control panel" app

Nagios does seem a bit overkillish, especially given that the "processes" I'm monitoring are more "Hello world" than "netstat". : )

It's cool that it even monitors temperature, though.

As for cron, the thing is that I have to evaluate when to stop/start each of the processes, so having them run at set times every day/hour/whatever would be a bad thing.

Comment on Re^2: CGI "control panel" app

Replies are listed 'Best First'.
Re^3: CGI "control panel" app by leocharre (Priest) on Jul 26, 2007 at 13:13 UTC
How do you evaluate when to stop or start? You the human being is who judges? What is an example of when to stop? When a certain cpu boundary is met? When something appears o n the screen? Is what these shell programs do just to retreive information and report it back? What would an example evalution be which you think you need a human being's intervention? I have a feeling whatever it is it could be logged, sent to you via email, triggered by a set of system conditions, etc. I'm sure you know this already; If you state an example of one of these programs, what it should do - not how - you will be shocked with how many ideas are out here from your perl brethren. You want to put a nail on a wall, but someone out here will show you how you can make the wall lie down on the nails and get them all in at once instead! I've had a lot of those moments here. Some of the things I would be curious about here concern security, not so much if these things can be done. Is this something only people with clearance would use? That is, someone who can usually root into the system would be using this (aside of what user the process runs as), just curious.	[reply]

Replies are listed 'Best First'.

Re^3: CGI "control panel" app
by leocharre (Priest) on Jul 26, 2007 at 13:13 UTC

How do you evaluate when to stop or start? *You* the human being is who judges? What is an example of when to stop? When a certain cpu boundary is met? When something appears o n the screen? Is what these shell programs do just to retreive information and report it back? What would an example evalution be which you think you need a human being's intervention? I have a feeling whatever it is it could be logged, sent to you via email, triggered by a set of system conditions, etc.

I'm sure you know this already; If you state an example of one of these programs, *what* it should do - not *how* - you will be shocked with how many ideas are out here from your perl brethren. You want to put a nail on a wall, but someone out here will show you how you can make the wall lie down on the nails and get them all in at once instead! I've had a lot of those moments here.

Some of the things I would be curious about here concern security, not so much *if* these things can be done.

Is this something only people with clearance would use? That is, someone who can usually root into the system would be using this (aside of what user the process runs as), just curious.

[reply]