rsyslog
May 17, 2008 - 11:33 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.

Topic: Change Log

The new items published under this topic are as follows.

<   12345678910    

rsyslog 1.0.0
Version 1.0.0 (RGer), 2005-09-12

  • changed install doc to cover daily cron scripts - a trouble source
  • added rc script for slackware (provided by Chris Elvidge - thanks!)
  • fixed a really minor bug in usage() - the -r option was still reported as without the port parameter

This is the first (officially) stable release of rsyslog.


Posted by  rgerhards  on  Thursday, September 08, 2005 678
 Send this story to someone Printer-friendly page 

Changelog for 0.9.8 - 2005-09-05
Version 0.9.8 (RGer), 2005-09-05

  • made startup and shutdown message more consistent and included the pid, so that they can be easier correlated. Used syslog-protocol structured data format for this purpose.
  • improved config info in startup message, now tells not only if it is listening remote on udp, but also for tcp. Also includes the port numbers. The previous startup message was misleading, because it did not say "remote reception" if rsyslogd was only listening via tcp (but not via udp).
  • added a "how can you help" document to the doc set


Posted by  rgerhards  on  Monday, September 05, 2005 751
 Send this story to someone Printer-friendly page 

Changelog for 0.9.7 - 2005-08-15
Version 0.9.7 (RGer), 2005-08-15
  • some of the previous doc files (like INSTALL) did not properly reflect the changes to the build process and the new doc. Fixed that.
  • changed syslogd.c so that when compiled without database support, an error message is displayed when a database action is detected in the config file (previously this was used as an user rule ;))
  • fixed a bug in the os-specific Makefiles which caused MySQL support to not be compiled, even if selected


Posted by  therget  on  Monday, August 15, 2005 1143
 Send this story to someone Printer-friendly page 

Changelog for 0.9.6 - 2005-08-09
Version 0.9.6 (RGer), 2005-08-09

IMPORTANT: The 0.9.6 release has a build procedure different from previous versions of rsyslog. It has been reported that this causes confusion and is not very obvious in the supporting doc. Please be sure to have a look the rsyslog install man page before you build it.

  • greatly enhanced documentation. Now available in html format in the "doc" folder and FreeBSD. Finally includes an install howto.
  • improved MySQL error messages a little - they now show up as log messages, too (formerly only in debug mode
  • added the ability to specify the listen port for udp syslog. WARNING: This introduces an incompatibility. Formerly, udp syslog was enabled by the -r command line option. Now, it is "-r [port]", which is consistent with the tcp listener. However, just -r will now return an error message.
  • added sample startup scripts for Debian and FreeBSD
  • added support for easy feature selection in the makefile. Unfortunately, this also means I needed to spilt the make file for different OS and distros. There are some really bad syntax differences between FreeBSD and Linux make.


Posted by  rgerhards  on  Tuesday, August 09, 2005 1293
 Send this story to someone Printer-friendly page 

Changelog for 0.9.5 - 2005-08-01
Version 0.9.5 (RGer), 2005-08-01

  • the "semicolon bug" was actually not (fully) solved in 0.9.4. One part of the bug was solved, but another still existed. This one is fixed now, too.
  • the "semicolon bug" actually turned out to be a more generic bug. It appeared whenever an invalid template name was given. With some selector actions, rsyslogd dumped core, with other it "just" had a small ressource leak with others all worked well. These anomalies are now fixed. Note that they only appeared during system initaliziation once the system was running, nothing bad happened.
  • improved error reporting for template errors on startup. They are now shown on the console and the start-up tty. Formerly, they were only visible in debug mode.
  • support for multiple instances of rsyslogd on a single machine added
  • added new option "-o" --> omit local unix domain socket. This option enables rsyslogd NOT to listen to the local socket. This is most helpful when multiple instances of rsyslogd (or rsyslogd and another syslogd) shall run on a single system.
  • added new option "-i <pidfile>" which allows to specify the pidfile. This is needed when multiple instances of rsyslogd are to be run.


Posted by  rgerhards  on  Monday, August 01, 2005 1032
 Send this story to someone Printer-friendly page 

Changlog for 0.9.4 - 2005-07-25
Version 0.9.4 (RGer), 2005-07-25

  • finally added the TCP sender. It now supports non-blocking mode, no longer disabling message reception during connect. As it is now, it is usable in production. The code could be more sophisticated, but I've kept it short in anticipation of the move to liblogging, which will lead to the removal of the code just written ;)
  • the "exiting on signal..." message still had the "syslogd" name in it. Changed this to "rsyslogd", as we do not have a large user base yet, this should pose no problem.
  • changed a default for traditional output format. During testing, it was seen that the timestamp written to file in default format was the time of message reception, not the time specified in the TIMESTAMP field of the message itself. Traditionally, the message TIMESTAMP is used and this has been changed now.


Posted by  rgerhards  on  Monday, July 25, 2005 614
 Send this story to someone Printer-friendly page 

ChangeLog 0.9.3
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.


Posted by  therget  on  Tuesday, July 19, 2005 792
 Send this story to someone Printer-friendly page 

ChangeLog 0.9.2
Version 0.9.2 (RGer), around 2005-07-05

  • I intended to change the maxsupported message size to 32k to support IHE - but given the memory inefficiency in the usual use cases, I have not done this. I have, however, included very specific instructions on how to do this in the source code. I have also done some testing with 32k messages, so you can change the max size without taking too much risk.
  • added a syslog/tcp receiver; we now can receive messages via plain tcp, but we can still send only via UDP. The syslog/tcp receiver is the primary enhancement of this release.
  • slightly changed some error messages that contained a spurios \n at the end of the line (which gives empty lines in your log...)


Posted by  therget  on  Tuesday, July 05, 2005 740
 Send this story to someone Printer-friendly page 

ChangeLog 0.9.1
Changelog for rsyslog version 0.9.1 (RGer)

  • fixed code so that it compiles without errors under FreeBSD
  • removed now unused function "allocate_log()" from syslogd.c
  • changed the make file so that it contains more defines for different environments (in the long term, we need a better system for disabling/enabling features...)
  • changed some printf's printing off_t types to %lld and explicit (long long) casts. I tried to figure out the exact type, but did not succeed in this. In the worst case, ultra-large peta- byte files will now display funny informational messages on rollover, something I think we can live with for the next 10 years or so...


Posted by  therget  on  Tuesday, June 28, 2005 775
 Send this story to someone Printer-friendly page 

ChangeLog 0.9.0
Changelog for rsyslog version 0.9.0 (RGer)

  • changed the filed structure to be a linked list. Previously, it was a table - well, for non-SYSV it was defined as linked list, but from what I see that code did no longer work after my modifications. I am now using a linked list in general because that is needed for other upcoming modifications.
  • fixed a bug that caused rsyslogd not to listen to anything if the configuration file could not be read
  • previous versions disabled network logging (send/receive) if syslog/udp port was not in /etc/services. Now defaulting to port 514 in this case.
  • internal error messages are now supported up to 256 bytes
  • error message seen during config file read are now also displayed to the attached tty and not only the console
  • changed some error messages during init to be sent to the console and/or emergency log. Previously, they were only seen if the -d (debug) option was present on the command line.
  • fixed the "2gb file issue on 32bit systems". If a file grew to more than 2gb, the syslogd was aborted with "file size exceeded". Now, defines have been added according to http://www.daimi.au.dk/~kasperd/comp.os.linux.development.faq.html#LARGEFILE
    Testing revealed that they work ;) HOWEVER, if your file system, glibc, kernel, whatever does not support files larger 2gb, you need to set a file size limit with the new output channel mechanism.
  • updated man pages to reflect the changes


Posted by  therget  on  Wednesday, June 22, 2005 843
 Send this story to someone Printer-friendly page 

<   12345678910    

 Search
 
Google

 Last Forum Posts
 · Re: Transport With Stunnel-need your hel ...
Sorry, I overlooked the message. This looks like a duplicate port ...
· Re: if ... then ... else
I've re-read the whole thread. I think I now got it. Else is just ...
· Re: if ... then ... else
sandiso wrote:So I have many boxes and from few of those boxes I ...
· Re: if ... then ... else
You got me confused. I think my config is right but I`ll explain ...
· Re: if ... then ... else
Thanks for the files (received via mail). The problem was always ...

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


 Past Articles

:: Syndication: ::
Page created in 0.246458053589 seconds.