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

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

Change Log
Change Log  :: ChangeLog 0.9.3 ::
(968 Reads)  
Posted by therget on Tuesday, July 19, 2005 - 05:00 AM

Version 0.9.3 (RGer), 2005-07-19

  • fixed a bug in the message parser. In June, the RFC 3164 timestamp was not correctly parsed (yes, only in June and some other months, see the code comment to learn why...)
  • added the ability to specify the destination port when forwarding syslog messages (both for TCP and UDP)
  • added an very experimental TCP sender (activated by @@machine:port in config). This is not yet for production use. If the receiver is not alive, rsyslogd will wait quite some time until the connection request times out, which most probably leads to loss of incoming messages.

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