[rsyslog] desktop notifications from syslog

[david at lang.hm]

On Tue, 5 May 2009, Tom Metro wrote:

> david at lang.hm wrote:
>
>
>> you don't want to try and have dbus users push rules through dbus to
>> rsyslog. they can choose to ignore some of the stuff that they get, but
>> you don't want to go further than that.
>
> Again, this was a hypothetical future capability.
>
> The use case would be allowing a third party listener to interact with
> rsyslog without having to have the user (or the installer for that app.)
>  reconfigure rsyslog via its config file. That way the settings for
> that third party listener don't need to be put in two places.
>
> Of course the third party listener could always drop a file in
> /etc/rsyslog.d/, but consider a case where you have some GUI viewer of
> messages, and you want to let the user dynamically select the facilities
> or priorities that it monitors.
>
> An example of an application that permits 3rd party reconfiguration via
> DBus is Dnsmasq. An external process, like a resolvconf script, can
> inform Dnsmasq of a domain-specific DNS server to use dynamically after
> a VPN link is brought up. That's functionality that is beyond what can
> be achieved through the normal resolv.conf file, and it needs to happen
> dynamically.

I really don't think that it's a good idea to try and send lots of 
messages via DBUS, if you want a GUI logwatcher you really wouldn't want 
to tie it only to rsyslog. what you would want is something that recieves 
the full log stream through a pipe from the systems syslog daemon 
(sysklog, rsyslog, or syslog-ng) and then has it's own rules about wht to 
display.

David Lang