thanks for doing this,what you have is a good start.
wnother tidbit from git, between 3.22.0 and 5.7.1 there were 1388 commits,
with 11539 lines of commit logs (~6 lines per commit are boilerplate, but
that's still averaging about 4 lines of comment per commit)
DavidLang
On Mon, 8 Nov 2010,
Florian Riedl wrote:
David,
Rainer adressed me with the task to compile such a list.
A first draft can be found here:
http://www.rsyslog.com/features/
I will expand it a bit more and look up the version information that is yet
missing, which is still a lot.
Florian
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of [email protected]
Sent: Sonntag, 7. November 2010 08:36
To: rsyslog-users
Subject: Re: [rsyslog] difference from v. 3.22 and 5.4.0
On Sun, 7 Nov 2010, Harry Putnam wrote:
I run gentoo linux (kernel 2.6.33) and rsyslog version 3.22
In the course of a system update today, rsyslog version 5.4.0 was
installed, but it crashes immediately when started.
I've done no testing or diagnostics as yet, just went back to version
3.22. I wanted to find out first if there have been major changes that
might help diagnose the problem.
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
doing a little digging through git.
v5.7.1 has 835 files, 241044 lines, 997701 words, 8971232 characters
the diff between v.3.22.2 and v5.7.1 is 71367 lines long, and the diffstat
says 625 files changed, 45917 insertions(+), 9128 deletions(-)
Any tricky gotchas that might be involved?
oh yes. the locking has changed (a couple times), threading has improved
dramatically, parsing has been completely re-done, the ability to process
multiple messages at once has been added, the ability to bind
separate rulesets to inputs (and have the results ofone filter feed onto a
ruleset, in fact the entire concept of rulesets..), it's gained the
ability to load multiple parsers (either in a stack or tied to specific
inputs).
in the process it has gained a lot of capibilities and speed (improving by
at least two orders of magnatude) while keeping the logs at least as safe
as they were before.
as for where to start troubleshooting, the best thing to do with something
like this where it crashes on startup is to start it in debug mode and
read through the output. odds are you have some sort of fatal typo in the
config file and reading through the debug output as it parses the config
file will identify the error.
David Lang
P.S. Rainer, you really do need to do some sort of feture timeline to show
the drastic nature of what's changed. even if you just took a couple of
hours to do a git log and then wed out the merges and trivial commits, the
highlights that remain would be very impressinve and give people a good
idea how much more advanced 5.x is from 3.x
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
