<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.34">
<TITLE>RE: [syslog-ng] Upgrade from 1.6.11 to 2.0.7: Gotchas?</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks, Bazsi! I was wondering if there is anything documented on the upgrade path, or if there is anything documented on the downgrade if the upgrade is not successful. I like to have documents to fall back on, when I try to do something for the first time. :o) Thanks!!!</FONT></P>
<P><FONT SIZE=2>Chris Ivey</FONT>
</P>
<P><FONT SIZE=2>Affiliated Computer Services</FONT>
<BR><FONT SIZE=2>Enterprise Management Integration Services</FONT>
<BR><FONT SIZE=2>Infrastructure Management Senior Analyst</FONT>
</P>
<P><FONT SIZE=2>chris.ivey@acs-inc.com</FONT>
</P>
<P><FONT SIZE=2>"I have not failed, I have simply found 10,000 ways which do not work!" -- Thomas Edison</FONT>
<BR><FONT SIZE=2>"When you find yourself in a hole, the best thing to do is stop digging!" -- Nick Stokes</FONT>
<BR><FONT SIZE=2>"I reject your reality, and substitute my own!" -- Adam Savage</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: syslog-ng-bounces@lists.balabit.hu [<A HREF="mailto:syslog-ng-bounces@lists.balabit.hu">mailto:syslog-ng-bounces@lists.balabit.hu</A>] On Behalf Of Balazs Scheidler</FONT>
<BR><FONT SIZE=2>Sent: Sunday, January 13, 2008 3:10 AM</FONT>
<BR><FONT SIZE=2>To: Syslog-ng users' and developers' mailing list</FONT>
<BR><FONT SIZE=2>Subject: Re: [syslog-ng] Upgrade from 1.6.11 to 2.0.7: Gotchas?</FONT>
</P>
<BR>
<P><FONT SIZE=2>On Fri, 2008-01-11 at 08:03 -0600, Ivey, Chris wrote:</FONT>
<BR><FONT SIZE=2>> Folks, </FONT>
<BR><FONT SIZE=2>> I need to upgrade my syslog-ng from 1.6.11 to 2.0.7 since we</FONT>
<BR><FONT SIZE=2>> now are using devices with high resolution timestamps. As I inherited</FONT>
<BR><FONT SIZE=2>> these machines, and had not worked with syslog-ng prior to getting</FONT>
<BR><FONT SIZE=2>> them, I was wondering if anyone could let me know if there were any</FONT>
<BR><FONT SIZE=2>> gotchas for the upgrade. Can I upgrade in place? Do I need to make</FONT>
<BR><FONT SIZE=2>> backups of any files? Things of this nature. Thanks, all!</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
<P><FONT SIZE=2>You can upgrade in place, the 2.0 version is upward compatible with</FONT>
<BR><FONT SIZE=2>1.6.x, however as it is a complete rewrite, I'd suggest you to run the</FONT>
<BR><FONT SIZE=2>configuration file on a 2.0 first to see if it parses ok.</FONT>
</P>
<P><FONT SIZE=2>Once the configuration file is processed by the new version then most</FONT>
<BR><FONT SIZE=2>probably it will work well.</FONT>
</P>
<P><FONT SIZE=2>You can upgrade in place as if you encounter problems you can always go</FONT>
<BR><FONT SIZE=2>back to 1.6.x without pain.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Bazsi</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>syslog-ng maillist - syslog-ng@lists.balabit.hu</FONT>
<BR><FONT SIZE=2><A HREF="https://lists.balabit.hu/mailman/listinfo/syslog-ng" TARGET="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</A></FONT>
<BR><FONT SIZE=2>Frequently asked questions at <A HREF="http://www.campin.net/syslog-ng/faq.html" TARGET="_blank">http://www.campin.net/syslog-ng/faq.html</A></FONT>
</P>
</BODY>
</HTML>