[rsyslog-notify] Forum Thread: Re: installing rsyslog parallel to the official package - (Mode 'reply')

[noreply at adiscon.com]

User: dhaivat.desai 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24297#p24297

Message: 
----------
Hello,
I think running multiple version of rsyslog is not a problem.
Moreover I cannot uninstall official rsyslog from my machine as it is used
by some of the kernel modules too which I do not want to break.

I made sure that the custom rsyslog is installed as follow:
[b:2m7bodho]/usr/sbin/custom_rsyslogd
/usr/lib64/custom_rsyslog/*.so[/b:2m7bodho]

I prepared the rpm as well with name
[b:2m7bodho]custom_rsyslog-7.2.7-31.1.x86_64.rpm[/b:2m7bodho].

Moreover I also found from help of rsyslogd binary - 
usage: rsyslogd [-46AdnqQvwx] [-l<hostlist>] [-s<domainlist>]
                [-f<conffile>] [-i<pidfile>] [-N<level>]
[b:2m7bodho][-M<module load path>][/b:2m7bodho]
                [-u<number>]

So all I need to do is start custom_rsyslogd with -M option which in my
case points to [b:2m7bodho]/usr/lib64/custom_rsyslog[/b:2m7bodho].
I think for now we can live with this solution. All I was wondering that if
I can already make sure during compile time that the default location to
find rsyslog modules is not [b:2m7bodho]/usr/lib64[/b:2m7bodho] so that we
do not need to use -M config option when starting rsyslog.

Best Regards,
Dhaivat Desai.