[rsyslog] desktop notifications from syslog

Tom Metro tmetro+rsyslog at gmail.com
Tue May 5 08:14:19 CEST 2009


david at lang.hm wrote:
> I think the best way to do this is for the rsyslog output plugin to not 
> worry about who's listening. it just takes anything that the rsyslog rules 
> tell it to forward and sends it to DBUS.
> 
> at that point it's up to the admin to deal with the security issue about 
> what's going to be visable

I agree.

I was describing a potential future direction.


> 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.

  -Tom




More information about the rsyslog mailing list