MonitorWare Knowledge Base

Hello,
Just wanted to see if I could simply upgrade by compiling the new 1.11.1 code over 1.0.1 code?
I would like the new features so I am willing to upgrade, just wanted to make sure it would not make a mess of things.

Regards,
Javier

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

Well, you never know In theory, though, nothing should be messed up. It worked at least in my lab, which is the only environment I can authentically speak for.

Rainer

Rather than create a new thread I thought I'd stick with this one. Same question 2 major versions later. I want to upgrade from a previous version of 3 to the most recent. Should I just do the typical ./configure, make, make install and expect all of the old stuff be be overwritten?

Thanks!

That should work, but as usual: take care, no guarantees here

I'm trying to upgrade from 3.18 to 3.22 and am also adding the libdbi module to the installation in the process. I've tried to do './configure', 'make', 'make install' several times and after each try "rsyslogd -v" still reports a 3.18 version number. I suppose I could try it without the "--enable-libdbi" but it seems like there must be some other issue. Is there something simple that I'm missing?

Thanks!

I guess the pathes (e.g. --bindir) are different from the autotools defaults. I often have this myself on my x64 boxes.

I don't know why I didn't think of it earlier but a find command revealed that while the 3.18 binary was in '/usr/sbin/', the 3.22 version was in '/usr/local/sbin/'. Manually editing '/etc/init.d/rsyslog' resolved the issue.

Are there other file paths I should be concerned about?

Thanks Rainer!