Darren J Moffat wrote: > cindi wrote: >> Who is someone? sysevent is only good if 'someone' is listening. If >> its the admin you want to alert, an FMA ereport is more appropriate. >> ZFS already has a diagnosis engine that you could modify to understand >> the new ereport. > > I hadn't considered using FMA mainly because this isn't a fault but more > of an async event that someone needs to respond to.
I think we are talking about a problem to which you want to inform some human so that some action can be taken to correct that problem. This is what FMA is specifically designed to do. The only issue is that we may inform the wrong human (i.e. not the end user) as the FMA diagnosis goes to the ZFS agent, console, syslog and SNMP. > > The reason for suggesting a sysevent was because it allows multiple > different possibilities fow "who" is listening. One possible case is > that HAL picks up the sysevent and passes it to something in the users > GNOME session using DBUS. There's nothing preventing you from doing both: issue a sysevent and an ereport. The FMA team is also looking at how to integrate diagnoses into a desktop environment such that diagnoses are observable in the GNOME session. Cindi
