rsyslog
Oct 06, 2008 - 08:35 PM

Donate!
Satisfied with rsyslog?

Donate and help keep
the project alive!

Rainer's Blog

Login




 


 Log in Problems?
 New User? Sign Up!

Online
There are 36 unlogged users and 0 registered users online.

You can log-in or register for a user account here.

Change Log
Change Log  :: Changelog for 3.11.6 ::
(870 Reads)  
Posted by rgerhards on Wednesday, February 27, 2008 - 11:34 PM

Version 3.11.6 (rgerhards), 2008-02-27
  • bugfix: gssapi libraries were still linked to rsyslog core, what should no longer be necessary. Applied fix by Michael Biebl to solve this.
  • enabled imgssapi to be loaded side-by-side with imtcp
  • added InputGSSServerPermitPlainTCP config directive
  • split imgssapi source code somewhat from imtcp
  • bugfix: queue cancel cleanup handler could be called with invalid pointer if dequeue failed
  • bugfix: rsyslogd segfaulted on second SIGHUP tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=38
  • improved stability of queue engine
  • bugfix: queue disk file were not properly persisted when immediately after closing an output file rsyslog was stopped or huped (the new output file open must NOT have happend at that point) - this lead to a sparse and invalid queue file which could cause several problems to the engine (unpredictable results). This situation should have happened only in very rare cases. tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=40
  • bugfix: during queue shutdown, an assert invalidly triggered when the primary queue's DA worker was terminated while the DA queue's regular worker was still executing. This could result in a segfault during shutdown. tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=41
  • bugfix: queue properties sizeOnDisk, bytesRead were persisted to disk with wrong data type (long instead of int64) - could cause problems on 32 bit machines
  • bugfix: queue aborted when it was shut down, DA-enabled, DA mode was just initiated but not fully initialized (a race condition)
  • bugfix: imfile could abort under extreme stress conditions (when it was terminated before it could open all of its to be monitored files)
  • applied patch from varmojfekoj to fix an issue with compatibility mode and default module directories (many thanks!): I've also noticed a bug in the compatibility code; the problem is that options are parsed before configuration file so options which need a module to be loaded will currently ignore any $moddir directive. This can be fixed by moving legacyOptsHook() after config file parsing. (see the attached patch) This goes against the logical order of processing, but the legacy options are only few and it doesn't seem to be a problem.
  • bugfix: object property deserializer did not handle negative numbers

Send this story to someone  Printer-friendly page
Only logged in users are allowed to comment. register/log in
 Search
 
Google

 Last Forum Posts
 · Re: rsyslog performance
OK, I now have added a $UDPServerTimeRequery <nbr> ...
· Re: TLS fails to start on the client sid ...
no problem. I now see the error cause, looks like in some instanc ...
· Re: TLS fails to start on the client sid ...
Hi again,sorry for the UDP thing. My bad.This time TCP was used.M ...
· Re: rsyslog performance
Just a side-note: looking at the message parser (early stages), I ...
· Re: TLS fails to start on the client sid ...
Well... With that config, you can not get the error message you c ...



:: Syndication: ::
Page created in 0.126137018204 seconds.