Fri, 14 Oct 2005 09:03:45 +0200 http://www.liblogging.org/ PostNuke Powered Site en-us http://www.liblogging.org/images/logonew.gif http://www.liblogging.org/ internetadmins@adiscon.com http://www.liblogging.org/Article18.phtml There was a bug in the BEEP listeners which made them ignore the listen port set by srAPISetOption. The BEEP listeners always listen to 601, no matter what was set. This has today been fixed. The fix is currently available via anonymous CVS from sourceforge, only. Check there if you need this functionality. Fri, 14 Oct 2005 09:03:45 +0200 http://www.liblogging.org/Article17.phtml After a very long time, LibLogging 0.6.0 has been released today. This version is not as stable as 0.5.0, but it includes the COOKED listener as its most important feature (but please note that it currently does not support COOKED relay operations or is scheduled to do that in the near future). Mon, 03 Oct 2005 12:46:08 +0200 http://www.liblogging.org/Article16.phtml You may wonder... no news during the past month. Is LibLogging abandoned? Well, it looks like it is ... but that's not the truth. Of course, development on LibLogging has stopped, a fact caused by the simple matter of lack of interest in the library. However, there is growing interest since spring of this year and that interest will soon spawn some new development in LibLogging. There is a co-project, called rsyslog which implements a reliable syslog server, soon together with LibLogging. This project will hopefully create some additional awareness for RFC 3195 like logging. So, don't panic, LibLogging is still very vital alive, it was just resting a little bit. I expect some more updates coming within the next 3 month (there are already some new features in the CVS version). Rainer Gerhards Tue, 05 Jul 2005 14:45:52 +0200 http://www.liblogging.org/Article14.phtml The exact order of future development has not yet been decided, but it is likely that it will be close in the way the topics are ordered in this list: . . . . . . . . Mon, 26 Jan 2004 12:34:14 +0100 http://www.liblogging.org/Article13.phtml It comes with the addition of a client-side COOKED profile (not yet on the server side) as well as a full-blown message object. Mon, 26 Jan 2004 09:55:59 +0100 http://www.liblogging.org/Article12.phtml I will keep this version healthy as I move along. Only instable version will be found there for the time being (else use the ZIP archives). Mon, 26 Jan 2004 09:53:38 +0100 http://www.liblogging.org/Article11.phtml it is the world's first windows application doing so. See the news release for complete details. Mon, 26 Jan 2004 09:50:20 +0100 http://www.liblogging.org/Article10.phtml This version is the first one to include support for building servers (listeners). Please note that there is NO 0.3.0 version - this number was eaten up by an incomplete copy passed on to some limited folks. . . . . . . . . Mon, 26 Jan 2004 09:47:09 +0100 http://www.liblogging.org/Article9.phtml while the main project home page remains here, we will use the sourceforge discussion lists, forums and bug trackers. news release for complete details. Mon, 26 Jan 2004 09:43:03 +0100 http://www.liblogging.org/Article7.phtml The server runs and talks to other products. It needs a lot of polishing - I think we are still some days away from a public release. Mon, 26 Jan 2004 09:29:42 +0100 http://www.liblogging.org/Article6.phtml Adiscon's logger syslog command line tool.See news release for details. Fri, 23 Jan 2004 17:13:23 +0100 http://www.liblogging.org/Article5.phtml This is a stable build with a stable API. If you develop applications against the 0.2.0 API, these applications will work with all future versions of liblogging. Promised. So it is a good idea to being using it now. . . . . Fri, 23 Jan 2004 17:07:20 +0100 http://www.liblogging.org/Article4.phtml This is an interim version. It now compiles and runs cleanly under Linux (verified with Red Hat Linux 8.0). . . . . . . Fri, 23 Jan 2004 17:05:14 +0100 http://www.liblogging.org/Article3.phtml The (client side) API is now stable and should not need to be changed any time in the future. It is now up to around 3000 lines of code. Fri, 23 Jan 2004 16:58:52 +0100 http://www.liblogging.org/Article2.phtml Roughly 300 (very dirty) lines of code did the trick. Proof available online as part of beta 1 of Adiscon logger 1.1 tool. Please note that during the development we found some bugs in SDSC syslog and we have worked around them so that we could complete work. As such, logger 1.1beta1 work with SDSC syslogd 1.0.0 but not any higher release. Fri, 23 Jan 2004 16:09:41 +0100