rsyslog
Aug 30, 2008 - 09:35 AM

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 24 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 ::
(925 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
 · Mikrotik Logging, incorrect FROMHOST ...
I've got rsyslog and phplogcon all up and running but having one ...
· Re: wrong format from windows event log ...
Yes, that's exactly also my intention: all events from several W2 ...
· Re: wrong format from windows event log ...
Glad to hear it's working. I wouldn't count on the RFCs for a who ...
· Re: wrong format from windows event log ...
Yup... that's a miracle, as we say here in Italy... if you tell t ...
· Re: wrong format from windows event log ...
Thx, I didn't very well my homework... sorry.I'll try this and co ...

 Top Contributors
 
Contributor Contribs
varmojfekoj 7
Michael Biebl 2
Michel Biebl 1
Peter Vrabec 1



:: Syndication: ::
Page created in 0.125427007675 seconds.