rsyslog
Oct 06, 2008 - 09:19 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 32 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.12.1 ::
(613 Reads)  
Posted by rgerhards on Thursday, March 06, 2008 - 08:07 PM

Version 3.12.1 (rgerhards), 2008-03-06
  • added library plugins, which can be automatically loaded
  • bugfix: actions were not correctly retried; caused message loss
  • changed module loader to automatically add ".so" suffix if not specified (over time, this shall also ease portability of config files)
  • improved debugging support; debug runtime options can now be set via an environment variable
  • bugfix: removed debugging code that I forgot to remove before releasing 3.12.0 (does not cause harm and happened only during startup)
  • added support for the MonitorWare syslog MIB to omsnmp
  • internal code improvements (more code converted into classes)
  • internal code reworking of the imtcp/imgssapi module
  • added capability to ignore client-provided timestamp on unix sockets and made this mode the default; this was needed, as some programs (e.g. sshd) log with inconsistent timezone information, what messes up the local logs (which by default don't even contain time zone information). This seems to be consistent with what sysklogd did for the past four years. Alternate behaviour may be desirable if gateway-like processes send messages via the local log slot - in this case, it can be enabled via the $InputUnixListenSocketIgnoreMsgTimestamp and $SystemLogSocketIgnoreMsgTimestamp config directives
  • added ability to compile on HP UX; verified that imudp worked on HP UX; however, we are still in need of people trying out rsyslogd on HP UX, so it can not yet be assumed it runs there

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