Skip to main content

Restarting this blog

This was my personal blog that I abandoned ~10 years ago in favor of a corporate blog.  I am reviving it and continue where I left off.

This blog has focused a lot on technology and syslog-ng particular and that is something I don't want to change. I work a lot on home automation these days so I expect that to creep in.

It's difficult to explain a decade in a blog post but a few items follow that I consider noteworthy:

* syslog-ng became pretty successful as a commercial offering while still keeping the open source version in shape. In this 10 years the project produced 23 major syslog-ng releases with lots of new stuff open source first.

* Balabit a company has grown to 250+ employees EUR 20m+ revenue and was eventually sold to a US company called Quest/One Identity in 2018

* I left Balabit a year and a half later in 2019, the company behind syslog-ng, the one I was a founder of.

syslog-ng is still thriving and is gaining momentum. This is true for both the open source project and the commercial offering (at least that's what I hear from ex colleagues).

I am pretty fortunate that even though I sold my stake in Balabit I can keep my  hobby:  syslog-ng. And this is because of open source. In a way I am becoming an external contributor to a project I was once the corporate herald for. Neat, eh?

Now, enough rambling, it's pretty late. Blogging is on!

Comments

Popular posts from this blog

syslog-ng fun with performance

I like christmas for a number of reasons: in addition to the traditional "meet and have fun with your family", eat lots of delicious food and so on, I like it because this is the season of the year when I have some time to do whatever I feel like. This year I felt like doing some syslog-ng performance analysis. After reading Ulrich Deppert's series about stuff "What every programmer should know about memory" on LWN, I thought I'm more than prepared to improve syslog-ng performance. Before going any further, I'd recommend this reading to any programmer, it's a bit long but every second reading it is worth it. As you need to measure performance in order to improve it, I wrote a tool called "loggen". This program generates messages messages at a user-specifyable rate. Apart from the git repository you can get this tool from the latest syslog-ng snapshots. Loggen supports TCP, UDP and UNIX domain sockets, so really almost everything can be me...

syslog-ng OSE 2.1 released

I have just uploaded the first release in the syslog-ng Open Source Edition 2.1 branch to our website. It is currently only available in source format at this location: http://www.balabit.com/downloads/files/syslog-ng/sources/2.1/src This release synchronizes the core of syslog-ng to the latest PE version and adds the SQL destination driver. This is an alpha release and thus might be rough around the edges, but it basically only contains code already tested in the context of the Premium Edition. The SQL functionality requires a patched libdbi package, which is available at the same link. We're going to work on integrating all our libdbi related patches to the upstream package. If you want to know how the SQL logging works, please see the Administrator's Guide or our latest white paper Collecting syslog messages into an SQL database with syslog-ng. The latter describes the Premium Edition, but it applies to the Open Source one equally well.

syslog-ng 3.2 changes

I've just pushed a round of updates to the syslog-ng 3.2 repository, featuring some interesting stuff, such as: SQL reorganization: Patrick Hemmer sent in a patch to implement explicit transaction support instead of the previous auto-commit mode used by syslog-ng. I threw in some fixes and refactored the code somewhat. Configuration parser changes: the syntax errors produced by syslog-ng became much more user-friendly: not only the column is displayed, but also the erroneous line is printed and the error location is also highlighted. Additional plugin modules were created: afsql for the SQL destination, and afstreams for Solaris STREAMS devices. Creating a new plugin from core code takes about 15 minutes. I'm quite satisfied. With the addition of these two modules, it is now possible to use syslog-ng without any kind of runtime dependency except libc. The already existing afsocket module (providing tcp/udp sources & destinations) is compiled twice: once with and once withou...