rsyslog
Oct 06, 2008 - 08:34 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 35 unlogged users and 0 registered users online.

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

Change Log
Change Log  :: Changelog for 1.12.0 ::
(4437 Reads)  
Posted by rgerhards on Wednesday, October 26, 2005 - 04:56 PM

Version 1.12.0 (RGer), 2005-10-26, development branch

  • moved to a multi-threaded design. single-threading is still optionally available. Multi-threading is experimental!
  • fixed a potential race condition. In the original code, marking was done by an alarm handler, which could lead to all sorts of bad things. This has been changed now. See comments in syslogd.c/domark() for details.
  • improved debug output for property-based filters
  • not a code change, but: I have checked all exit()s to make sure that none occurs once rsyslogd has started up. Even in unusual conditions (like low-memory conditions) rsyslogd somehow remains active. Of course, it might loose a message or two, but at least it does not abort and it can also recover when the condition no longer persists.
  • fixed a bug that could cause loss of the last message received immediately before rsyslogd was terminated.
  • added comments on thread-safety of global variables in syslogd.c
  • fixed a small bug: spurios printf() when TCP syslog was used
  • fixed a bug that causes rsyslogd to dump core on termination when one of the selector lines did not receive a message during the run (very unlikely)
  • fixed an one-too-low memory allocation in the TCP sender. Could result in rsyslogd dumping core.
  • fixed a bug with regular expression support (thanks to Andres Riancho)
  • a little bit of code restructuring (especially main(), which was horribly large)

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.124887943268 seconds.