Ah, thanks Rainer. I have primarily worked on v5 and hardly tried to
migrate. That was an incoherent musing.

Thanks, I stand corrected.


On Thu, Apr 4, 2013 at 10:36 PM, Rainer Gerhards
<[email protected]>wrote:

> On Thu, 2013-04-04 at 22:28 +0530, Soham Chakraborty wrote:
> > Hi,
> >
> > I think a sane approach would be to note down the directives you are
> using
> > un v5 and then comparing them with v7 to see how they differ, in behavior
> > and documentation.
>
> This never happens in rsyslog. Once a directive and its behaviour is
> introduced, it is immutable, specifically to not break anything.
> However, some directives may become obsoleted, but that is rare.
> Differences can always be found in the compatibility notes, right from
> the main doc page. The most recent version is always available online:
>
> http://www.rsyslog.com/doc/manual.html
>
> Older versions are in the respective release tarballs.
>
> > If your syslog stuff is maintained/supported/used by
> > others, probably educate them too. Keep the working v5 config file handy
> so
> > that you can revert to v5, if things don't work as expected with v7 and
> you
> > need to debug.
> >
> > Particular use case testing is the best method that I can think of.
> >
> Testing is always a good idea, it is always possible that there is some
> regression nobody detected. Or that an old version did not properly
> catch an error in the config, where the new one does.
>
> As general advise, one should look at rsyslog startup messages
> (syslog.*). Many people do not record them and so are puzzled when
> things go wrong where otherwise a message is available that explains in
> plain words the cause ;)
>
> HTH
> Rainer
>
> > Soham
> >
> >
> > On Thu, Apr 4, 2013 at 9:24 PM, Josh Bitto <[email protected]>
> wrote:
> >
> > > Currently I'm running version rsyslog-5.8.10-6.el6.x86_64......So did
> some
> > > checking and there is a stable release of rsyslog 7.2.6 ST is
> available. I
> > > looked at the release notes and the bug fixes and should I be cautious
> when
> > > upgrading or is it pretty straight forward?
> > >
> > >
> > >
> > > Joshua Bitto
> > > Information Technologist
> > > KCC
> > >
> > >
> > >
> > > _______________________________________________
> > > 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.
> > >
> > _______________________________________________
> > 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.
>
> _______________________________________________
> 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.
>
_______________________________________________
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.

Reply via email to