[Bacula-users] RE: [Bacula-devel] PyGTK Console: about the tray icon
> Are you saying that instead I should write the tray icon to > reflect some status rather than problems? ie: showing the > number of running jobs. I may nave been confusing the tray icon for the client with a minimized icon/tray icon for operator interface you've been working on -- I occasionally get lost in the terminology, so please bear with me. If we are talking about the operator interface, then yes, I would probably expect to see running job state and error information indicated by flashing that icon somehow (something like a system console where messages are scrolling up as they come in). If you were referring to the client tray icon, then no, just errors or last job information is probably sufficient. One of the things to put on the wish list is a general message (in terms of job log items etc, not the current Bacula definition of "message") service. Someday when we all have too much free time...8-) --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] RE: [Bacula-devel] PyGTK Console: about the tray icon
> I'm sending this email to both lists because I think this is > od interest of both groups. > I haven't seen the already working bacula tray icon, and I > want to add to the PyGTK console, some sort tray icon so that > the operator can be noticed from interesting events. I think I would argue that the tray icon should notify the operator when ANY message is issued (ie, when any new messages are issued, blink or turn red or something), and use other methods (syslog, SNMP traps, etc) to handle failure alerts. Given that every operator I've ever observed ignores indicators like that, if it's important, it should be caught by some system that does not involve human reactions. Other than that, filtering messages is so site-specific that I doubt you could come up with a default set that would be useful. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Re: [Bacula-devel] PyGTK Console: about the tray icon
Hi David, David Boyes wrote: > I think I would argue that the tray icon should notify the operator when > ANY message is issued (ie, when any new messages are issued, blink or > turn red or something), and use other methods (syslog, SNMP traps, etc) > to handle failure alerts. > > Given that every operator I've ever observed ignores indicators like > that, if it's important, it should be caught by some system that does > not involve human reactions. Other than that, filtering messages is so > site-specific that I doubt you could come up with a default set that > would be useful. Are you saying that instead I should write the tray icon to reflect some status rather than problems? ie: showing the number of running jobs. Best regards, -- Lucas Di Pentima - Santa Fe, Argentina - Jabber ID: [EMAIL PROTECTED] LUNIX S.R.L. - Soluciones en GNU/Linux - http://www.lunix.com.ar GnuPG Public Key: http://random.sks.keyserver.penguin.de:11371/pks/lookup?op=get&search=0x6AA54FC9 Key fingerprint = BD3B 08C4 661A 8C3B 1855 740C 8F98 3FCF 6AA5 4FC9 signature.asc Description: OpenPGP digital signature
