On Fri, 2011-01-28 at 15:25 -0700, Lay, James wrote:

Hey All!

I’m about to do an upgrade from 3.0.1, to 3.2.2. Any surprises or gotchas I should be aware of? I’ve done some searching online and didn’t see too much in the way of what I needed to do, if anything, besides ./configure make and make install of eventlog and syslog-ng. My config below is what I am workin with:

@version:3.0

options { use_dns(no); };

source s_local {

unix-stream("/dev/log");

udp(ip(0.0.0.0) port(514));

tcp(ip(0.0.0.0) port(50000));

file("/proc/kmsg");

};

destination d_file {

file("/syslogs/messages");

};

log {

source(s_local);

destination(d_file);

};

Anything besides changing the version number? Thanks all.

Well, my intention has always been not to cause upgrade gotchas. With a simple config like your it should be easy. But anyway, it is good practice to start in a separate test environment rather than doing it in production. -- Bazsi