Most applications that call syslog(3) from the C library seem to write to /dev/log by default
The openlog(3) call doesn't appear to have any option to override the socket name Is anybody familiar with any method that can be used to override the socket name, for example, if I want some applications to log to /dev/testlog for a separate instance of rsyslogd to monitor? The only two things that come to mind so far: - running the application in a chroot - using LD_PRELOAD to load some lib that intercepts calls to connect() and changes the argument when it is /dev/log although if there is a more lightweight solution (like an environment variable that syslog(3) recognises) I would prefer to use it _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
