[syslog-ng] Parallel Use of syslog-ng with syslogd (Linux RH ES4)

[Fegan, Joe]

> are there supplied hooks to routines equivalent to syslog(3) in the C library?

syslog-ng can function as a drop-in replacement for syslogd, applications will not notice anything has changed. When an application uses the system call syslog() on Linux all that really happens is that the message is sent to the socket /dev/log. It is assumed that some daemon is listening and writing down whatever it hears. Normally the listener is syslogd but you can replace it with any other listener (e.g. syslog-ng) and the calling application will have no idea that anything has changed.

________________________________
From: syslog-ng-bounces at lists.balabit.hu [mailto:syslog-ng-bounces at lists.balabit.hu] On Behalf Of Diffenderfer, Randy
Sent: 04 March 2008 12:23
To: syslog-ng at lists.balabit.hu
Subject: [syslog-ng] Parallel Use of syslog-ng with syslogd (Linux RH ES4)


Folks,

I haven't yet done the research here by RTFS'ing, so I apologize in advance for uninformed posting... :-)

I'm looking at syslog-ng as a syslogd replacement in our shop.  I'd like to determine in advance if there is a reasonable way to run these in parallel.

In particular, are there supplied hooks to routines equivalent to syslog(3) in the C library?  I understand that I can shut down syslogd and bring up syslog-ng listening to /dev/log, and things will be transparent to production code.  I envision an environment where I have the RH syslogd listening to /dev/log, and syslog-ng listening to /dev/log-ng.  Using perl and C routines, can I integrate my production code with minimal alterations to selectively use the new facility?

Thanks for any advice,
rnd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20080304/fface560/attachment.htm