On Mon, 8 Nov 2010, Harry Putnam wrote:
[email protected] writes:
the changes between 3.22 and 5.4 are huge. you would have to go though
the git tree to see them all, but that's such a huge amont of
development that it's not really practical
Thanks... good info there.
About starting in debug mode as suggested, is it possible to do that
on a machine running a working version or will it really jack up
existing logging?
I guess what I'm asking is how to debug in a sandbox. Some way to run
the newest version without bothering the current system logger.
if you add the -d option to the command line at startup time, rsyslog will
spew out a HUGE amount of data to stdout, it won't affect anything else on
the system. you may not even need to stop the running copy (if there is a
conflict with the running copy, it will show up in the output, at which
time you can re-run the test after stopping the running copy)
In your case, I think the problem sounds like a config file error, so jus
tthe startup debug messages are probably enough.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
