On Wed, 2008-11-26 at 13:52 -0800, Matt Camuto wrote:
Hi There –
I am new to this group so I thank you in advance for any help. We are in the process of evaluating syslog-ng for a replacement for normal syslogd. However it is desired for a few months to have syslog-ng and syslogd running on the same box with syslog-ng simply not handling the normal ‘syslog traffic’ (udp/514). We currently have a 30 day eval license to test out syslog-ng. We are using a sun t1000 box as an fyi.
When we install syslog-ng the install script informs us that syslogd will be removed as a service?!?!
Has anybody ever run syslogd (in either agent or server mode) on the same machine with syslogd running. Any guidance there would be highly appreciated. We are not in the position to do a hard cross over to syslog-ng for our production environment.
Well, I guess you are using the new syslog-ng 3.0 installer, which does way more than the previous ones to make it easier to deploy syslog-ng. But you are right, its model is to disable the stock syslogd and replace it with syslog-ng. However it is possible to skip the installation script, in which case only the binaries are loaded to the machine and no installation is performed. If you run the installation program with the --noexec argument, the embedded installation script will not be run, but still the contents of the archive are extracted. Basically the .run file is a self-extracting tar file. Once you have the binaries, you are free to change your system in a way that lets you run both syslogd and syslog-ng at the same time. Since their files on the disk do not conflict, and it is possible to create configurations for both that do not conflict, it is certainly possible to run the two in parallel. -- Bazsi