User: Password:
|
|
Subscribe / Log in / New account

A licensing change for syslog-ng

A licensing change for syslog-ng

Posted Aug 31, 2010 18:38 UTC (Tue) by kerick (subscriber, #53036)
Parent article: A licensing change for syslog-ng

Personally, I'd rather use rsyslog anyway. Most of the features are there, it's multithreaded, and is GPLv3 ("http://www.rsyslog.com/doc/manual.html").


(Log in to post comments)

A licensing change for syslog-ng

Posted Aug 31, 2010 23:38 UTC (Tue) by ESRI (guest, #52806) [Link]

I do like syslog-ng's configuration file format oh so much better though. :)

A licensing change for syslog-ng

Posted Sep 1, 2010 8:23 UTC (Wed) by bazsi (guest, #63084) [Link]

As I understand rsyslog has the same licensing structure as syslog-ng 3.2 minus the GPL version (rsyslog is using GPLv3, syslog-ng is GPLv2 or later), at least according to this article:

http://www.rsyslog.com/doc/licensing.html

I wouldn't go into feature comparison as I'm biased (as the author of syslog-ng).

Full multithreading is coming in syslog-ng OSE 3.3, see this blog post & code:

http://bazsi.blogs.balabit.com/2010/09/multi-threading-co...

A licensing change for syslog-ng

Posted Sep 3, 2010 1:36 UTC (Fri) by nevyn (guest, #33129) [Link]

Indeed, despite it being multi-threaded and GPLv3 rsyslog is pretty good.

A licensing change for syslog-ng

Posted Sep 8, 2010 13:46 UTC (Wed) by johoho (subscriber, #2773) [Link]

In our company we ditched rsyslog in favour of syslog-ng premium over a year ago and we are very satisfied with it. Rsyslog did regularily loose loglines, cut off too long lines or stalled the complete machine. Support was not available and after 4 or 5 tries on the mailing lists we eventually gave up.
Nowadays we run OSE on the clients and have premium edition on loghosts and we did not loose a single logline since.
Admitted, it is expensive. But maybe we will get a fork or additional GPL plugins providing reliable log transport in the future.

A licensing change for syslog-ng

Posted Sep 8, 2010 18:50 UTC (Wed) by bazsi (guest, #63084) [Link]

As the original author of syslog-ng I'd really like to know what blocks the deployment of the PE on the clients. License wise those should already be covered. Is it a technical reason? Are you using distribution provided OSE packages?

Feel free to send email or post it here as you feel appropriate.

A licensing change for syslog-ng

Posted Sep 9, 2010 10:09 UTC (Thu) by johoho (subscriber, #2773) [Link]

Hi,

sorry, my fault. We do use PE on clients, too.

A licensing change for syslog-ng

Posted Sep 10, 2010 7:50 UTC (Fri) by nix (subscriber, #2304) [Link]

we did not loose a single logline since
I'm another happy syslog-ng user (the database and parser support *rock*, who needs separate log analysis programs anyway?) but I find myself wondering... if unimportant log lines were silently vanishing in transit, how would you know?

:)

A licensing change for syslog-ng

Posted Sep 10, 2010 8:41 UTC (Fri) by johoho (subscriber, #2773) [Link]

Initally we were using standard syslog daemon for local and remote logging. Over time we had some network trouble and were forced to re-transmit loglines to central logging server. Since we store all logs for 30 days local, this was not a problem. This local log was used to compare lines on the CLS with the local copies. If line count does not match, you have a problem.

PS: oh yes, rsyslog had trouble with remote / local loglines not being identical..


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds