|
| From: | Chip Seraphine |
| Subject: | Cfengine Feature Wish List? |
| Date: | Wed, 14 May 2003 14:08:38 -0500 |
| User-agent: | Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.2.1) Gecko/20030121 |
In ascending order of implementation (by my estimate, which may be way off):1) A control: option that allows selection of the syslog facility CFEngine uses, allowing administrators to (for instance) send all cfengine messages to a localN facility. (I already have [locally] a crude compile-time patch for this, email me if you want it.)
2) Corresponding negatives/positives for the various WarnIf and BeginGroup edittools. This would reduce the kludgery sometimes needed to Do The Right Thing.
3) Add options to the alert: functionality to control the medium by which the alert is sent, eg syslog, stderr, pipe into a command, etc. As mentioned below, SNMP would be very attractive although a little more work to implement.
4) A means of having modules execute conditionally. True, you can control their behavior by passing classes, but you still have to fire up the perl interpreter or whatever to get there. I was imagining it would be great to have a "modules:" section and operate them more like shellcommands rather than purely out of the actionsequence. This would reduce the difference between a shellcommand and a module to basically just the setting/unsetting classes mechanism, which (if I understand correctly) is supposed to be the difference anyhow.
#3 and #4 above would involve more cranking on cfengine than I feel brave enough to do, but I'd be happy to work on the first two if there is interest from the list and/or Mark wants a patch for 'em.
mark@iu.hio.no wrote:
Why not reply to the list with a Wish List and see what happens? M On 14 May, Chip Seraphine wrote:That would be very, very nice indeed! <he says, wiping drool off the keyboard> mark@iu.hio.no wrote:Perhaps an alert function that sends directly to syslog could be added. Other types of alerts could be generated too, e.g. SNMP traps. M On 14 May, Chip Seraphine wrote:I have a kludgey alert system in place-- I define a class ("complain"), which causes a shellscript to kick off that analyzes $CFALLCLASSES and generates appropriate notifications (turning on lights in NMS, sending out emails/pages, etc). This works fine, but seems like it should not be neccessary given that cfengine supports an "alerts:'"section. Unfortunately, I haven't seen a good way to get an alert to go to syslog instead of stdout-- just ugly hacks like redirecting cfengine output. The syslog() option in control: seems to be ignored by alerts... Am I missing something?If not, then maybe we could put that down as a feature request-- an option that can be added to alerts that would allow you to send alert messages to syslog (at a specific priority) so that my network monitoring system can handle it. Or, at the least, send a copy of the alert to syslog if Syslog( on ) is set...._______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://mail.gnu.org/mailman/listinfo/help-cfengine~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Work: +47 22453272 Email: Mark.Burgess@iu.hio.no Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Work: +47 22453272 Email: Mark.Burgess@iu.hio.no Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| [Prev in Thread] | Current Thread | [Next in Thread] |