Package: sensord Version: 1:2.9.0-6 Followup-For: Bug #243610 I disagree with this wishlist: i believe a tool has a job . If you had mail support, then why not sms ? or maybe store the data in a db so i can find out whether it was only a one shot error without having to grep teh logs ... its an asap alert after all .
logcheck is not a tool for asap alerts (it s more of a trend tool that a realtime one , isn't it ?), though it s far from the only alert tool out there. I feel moodss (gui/optional db) and moopss (daemon/db) are dedicated tools for this kind of task . I guess there are a lot more to find out. from memory i would tell cactus/rrdtools . By now smartmontools has its db and alert mechanism, snort does too , and so goes on . My bet are this render those tools harder to maintain, less secure, memory and i/o hogs ... and not the least , not integrated at all . One has to find out each one config syntax and storage peculiarities. The bad point is that those monitoring tools are in no way integrated with the daemons they are monitoring, be it backup , hardware failue ... That s distro/debian job btw to integrate tools, What if every tools has its own cron daemon ? As we are far from a debian monitoring policy (an /etc/monitor.d as cron.d or init.d mananged by postinstall ?, sarge +10 i guess), maybe that mail alert thing is a must . But please do not go beyond that (db backend, sms who knows ...) PS: i already bugged moodss maintenair to have moopss in debian. I am all for a monitoring policy , though feeel that will have to wait for a lot of other stuff getting in the debian framework (db config policy, bootlog rewrite). I bet i am dreaming . Though tools like moopss/logcheck enable us admins to do realtime/trend monitoring data storage and alert right now. If someone want every monitoring tool like smart/sensrod/snort to do its own storage and alert, the way debian leave you on your own to configure the real storage/alert tools, it can be understood. It s way easier to add an email line in sensord config file than installing and configuring cactus and the like. Cheers Alban -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages sensord depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii librrd0 1.0.49-1 Time-series data storage and displ ii libsensors3 1:2.9.0-6 Library to read temperature/voltag ii lm-sensors 1:2.9.0-6 Utilities to read temperature/volt -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
