syslog-ng maintenance changes
Hi, I had a decreasing amount of time to work on syslog-ng in the past year, as you may have noticed by my absense on the mailing list, and the relative rarity of my blog posts. More and more is done by Algernon (aka Gergely Nagy), and I felt it to be incorrect to be the bottleneck in a number of cases. Even though Algernon is emloyed by BalaBit, his daily job didn't and doesn't mandate such close relationship with syslog-ng. That was his own motivation, and I think that is a key to maintaining or developing open source software. After talking to him in real life, we've decided to make a shift, he is going to maintain the 3.3 tree and making releases instead of myself. This will make 3.3 maintenance smoother, and free some precious time for me, which I'd use to work on the 3.4 features. The location of the syslog-ng trees will change too, they would be available at: git://github.com/balabit/syslog-ng-3.3.git git://github.com/balabit/syslog-ng-3.4.git or the web interface at: http://github.com/balabit I am certain that this change is for the better of syslog-ng, and I hope the conclusion of the community will be the same in a few months. I really thank him for helping me out. Cheers, Bazsi
Hi! Balazs Scheidler <bazsi@balabit.hu> writes:
After talking to him in real life, we've decided to make a shift, he is going to maintain the 3.3 tree and making releases instead of myself. This will make 3.3 maintenance smoother, and free some precious time for me, which I'd use to work on the 3.4 features.
I'd like to take this opportunity to outline my plans with regards to 3.3, and provide a short roadmap. There won't be many changes, as 3.3 is a stable release afterall, and I want to keep it that way. The latest 3.3.5 release was already almost perfect, and by far the best 3.3 release so far, I'd like to make 3.3.6 top that. As of now, the following items are on the 3.3.6 roadmap: [X] systemd enhancements: [X] Correctly alias syslog-ng.service to syslog.service [X] Teach the system() source about systemd, so configs using system() will work on both systemd-enabled systems, and traditional ones as well, without change. [X] Smooth transition from /dev/log to journal: if systemd is in use, and the config uses /dev/log, translate that to /run/systemd/journal/syslog. This will go away post-3.4! [ ] Include man page and admin guide references in the Documentation= section of the unit file. [X] Ignore SIGHUP in the supervisor [#143] [X] Don't use deprecated glib symbols: a purely cosmetic change, to reduce the number of compile-time warnings on modern systems. [X] Restore fsync(yes) functionality [#175] [X] README in spec, but not in source [#180] [ ] Fix unix-dgram's handling of charset decoding errors [#181] [ ] Fix spoofed source on Solaris [#178] [ ] Fix ivykis-related run-time error on mips64 [#176] [#143]: https://bugzilla.balabit.com/show_bug.cgi?id=143 [#175]: https://bugzilla.balabit.com/show_bug.cgi?id=175 [#181]: https://bugzilla.balabit.com/show_bug.cgi?id=181 [#178]: https://bugzilla.balabit.com/show_bug.cgi?id=178 [#176]: https://bugzilla.balabit.com/show_bug.cgi?id=176 [#180]: https://bugzilla.balabit.com/show_bug.cgi?id=180 Apart from these, there's one major thing I want to change, which will - by default - not affect anyone, but I have hopes that it will prove to be beneficial in the future (and as a side effect, also fixes #176): starting with syslog-ng 3.3.6, along with the tarball, a patch file will be provided too, that makes it possible to use upstream ivykis with syslog-ng, instead of the embedded, forked copy it ships with now. This means that distributions will be able to compile syslog-ng against a packaged ivykis, and any bugs found therein, will be easier to fix, and any improvements made to ivykis will also benefit syslog-ng immediately. This also paves the way to switching to upstream ivykis by default at a later point in time - but that switch is out of the scope of a stable series, so it can only be done in 3.4 soonest. Nevertheless, an optional patch to make this easy is a worth the effort, I believe. And that's all there is, the only remaining question is: when will 3.3.6 land? I'm a firm believer of the Debianesque "when it is ready" school, so as soon as the list above has all boxes ticked, and there are no new issues to solve, I'll hit the release button. I expect that to happen in a couple of weeks, mid-June or so, if all goes well. That way we might even have 3.3.6 in Debian Wheezy, using upstream ivykis, which would make me *very* happy. -- |8]
Can you please also fix bug 159 https://bugzilla.balabit.com/show_bug.cgi?id=159 It causes me pain almost weekly, and soon to be hourly as we automate the production of the patterndb from a SQL database engine which will result in a HUP very often. Evan. Gergely Nagy wrote:
Hi!
Balazs Scheidler <bazsi@balabit.hu> writes:
After talking to him in real life, we've decided to make a shift, he is going to maintain the 3.3 tree and making releases instead of myself. This will make 3.3 maintenance smoother, and free some precious time for me, which I'd use to work on the 3.4 features.
I'd like to take this opportunity to outline my plans with regards to 3.3, and provide a short roadmap. There won't be many changes, as 3.3 is a stable release afterall, and I want to keep it that way. The latest 3.3.5 release was already almost perfect, and by far the best 3.3 release so far, I'd like to make 3.3.6 top that.
As of now, the following items are on the 3.3.6 roadmap:
[X] systemd enhancements: [X] Correctly alias syslog-ng.service to syslog.service [X] Teach the system() source about systemd, so configs using system() will work on both systemd-enabled systems, and traditional ones as well, without change. [X] Smooth transition from /dev/log to journal: if systemd is in use, and the config uses /dev/log, translate that to /run/systemd/journal/syslog. This will go away post-3.4! [ ] Include man page and admin guide references in the Documentation= section of the unit file. [X] Ignore SIGHUP in the supervisor [#143] [X] Don't use deprecated glib symbols: a purely cosmetic change, to reduce the number of compile-time warnings on modern systems. [X] Restore fsync(yes) functionality [#175] [X] README in spec, but not in source [#180] [ ] Fix unix-dgram's handling of charset decoding errors [#181] [ ] Fix spoofed source on Solaris [#178] [ ] Fix ivykis-related run-time error on mips64 [#176]
[#143]: https://bugzilla.balabit.com/show_bug.cgi?id=143 [#175]: https://bugzilla.balabit.com/show_bug.cgi?id=175 [#181]: https://bugzilla.balabit.com/show_bug.cgi?id=181 [#178]: https://bugzilla.balabit.com/show_bug.cgi?id=178 [#176]: https://bugzilla.balabit.com/show_bug.cgi?id=176 [#180]: https://bugzilla.balabit.com/show_bug.cgi?id=180
Apart from these, there's one major thing I want to change, which will - by default - not affect anyone, but I have hopes that it will prove to be beneficial in the future (and as a side effect, also fixes #176): starting with syslog-ng 3.3.6, along with the tarball, a patch file will be provided too, that makes it possible to use upstream ivykis with syslog-ng, instead of the embedded, forked copy it ships with now.
This means that distributions will be able to compile syslog-ng against a packaged ivykis, and any bugs found therein, will be easier to fix, and any improvements made to ivykis will also benefit syslog-ng immediately.
This also paves the way to switching to upstream ivykis by default at a later point in time - but that switch is out of the scope of a stable series, so it can only be done in 3.4 soonest. Nevertheless, an optional patch to make this easy is a worth the effort, I believe.
And that's all there is, the only remaining question is: when will 3.3.6 land? I'm a firm believer of the Debianesque "when it is ready" school, so as soon as the list above has all boxes ticked, and there are no new issues to solve, I'll hit the release button.
I expect that to happen in a couple of weeks, mid-June or so, if all goes well. That way we might even have 3.3.6 in Debian Wheezy, using upstream ivykis, which would make me *very* happy.
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Unix Services, University Systems, University of Victoria
On Wed, May 30, 2012 at 7:04 PM, Evan Rempel <erempel@uvic.ca> wrote:
Can you please also fix bug 159
https://bugzilla.balabit.com/show_bug.cgi?id=159
It causes me pain almost weekly, and soon to be hourly as we automate the production of the patterndb from a SQL database engine which will result in a HUP very often.
I could've sweared I fixed something like that before, twice. Added it to the 3.3.6 TODO list, thanks for the heads-up! -- |8]
I know Gergely Nagy is working very hard to get 3.3.6 out the door, but I wanted to add one more (easy) thing to the bug list for this release. Bug 147 included the patterndb-4.xsd file into the source tarball, but it was not added to the doc/Makefile.in I have attached a patch that fixes this. Evan. ________________________________________ From: Evan Rempel [erempel@uvic.ca] Sent: Wednesday, May 30, 2012 10:04 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] syslog-ng maintenance changes Can you please also fix bug 159 https://bugzilla.balabit.com/show_bug.cgi?id=159 It causes me pain almost weekly, and soon to be hourly as we automate the production of the patterndb from a SQL database engine which will result in a HUP very often. Evan. Gergely Nagy wrote:
Hi!
Balazs Scheidler <bazsi@balabit.hu> writes:
After talking to him in real life, we've decided to make a shift, he is going to maintain the 3.3 tree and making releases instead of myself. This will make 3.3 maintenance smoother, and free some precious time for me, which I'd use to work on the 3.4 features.
I'd like to take this opportunity to outline my plans with regards to 3.3, and provide a short roadmap. There won't be many changes, as 3.3 is a stable release afterall, and I want to keep it that way. The latest 3.3.5 release was already almost perfect, and by far the best 3.3 release so far, I'd like to make 3.3.6 top that.
As of now, the following items are on the 3.3.6 roadmap:
[X] systemd enhancements: [X] Correctly alias syslog-ng.service to syslog.service [X] Teach the system() source about systemd, so configs using system() will work on both systemd-enabled systems, and traditional ones as well, without change. [X] Smooth transition from /dev/log to journal: if systemd is in use, and the config uses /dev/log, translate that to /run/systemd/journal/syslog. This will go away post-3.4! [ ] Include man page and admin guide references in the Documentation= section of the unit file. [X] Ignore SIGHUP in the supervisor [#143] [X] Don't use deprecated glib symbols: a purely cosmetic change, to reduce the number of compile-time warnings on modern systems. [X] Restore fsync(yes) functionality [#175] [X] README in spec, but not in source [#180] [ ] Fix unix-dgram's handling of charset decoding errors [#181] [ ] Fix spoofed source on Solaris [#178] [ ] Fix ivykis-related run-time error on mips64 [#176]
[#143]: https://bugzilla.balabit.com/show_bug.cgi?id=143 [#175]: https://bugzilla.balabit.com/show_bug.cgi?id=175 [#181]: https://bugzilla.balabit.com/show_bug.cgi?id=181 [#178]: https://bugzilla.balabit.com/show_bug.cgi?id=178 [#176]: https://bugzilla.balabit.com/show_bug.cgi?id=176 [#180]: https://bugzilla.balabit.com/show_bug.cgi?id=180
Apart from these, there's one major thing I want to change, which will - by default - not affect anyone, but I have hopes that it will prove to be beneficial in the future (and as a side effect, also fixes #176): starting with syslog-ng 3.3.6, along with the tarball, a patch file will be provided too, that makes it possible to use upstream ivykis with syslog-ng, instead of the embedded, forked copy it ships with now.
This means that distributions will be able to compile syslog-ng against a packaged ivykis, and any bugs found therein, will be easier to fix, and any improvements made to ivykis will also benefit syslog-ng immediately.
This also paves the way to switching to upstream ivykis by default at a later point in time - but that switch is out of the scope of a stable series, so it can only be done in 3.4 soonest. Nevertheless, an optional patch to make this easy is a worth the effort, I believe.
And that's all there is, the only remaining question is: when will 3.3.6 land? I'm a firm believer of the Debianesque "when it is ready" school, so as soon as the list above has all boxes ticked, and there are no new issues to solve, I'll hit the release button.
I expect that to happen in a couple of weeks, mid-June or so, if all goes well. That way we might even have 3.3.6 in Debian Wheezy, using upstream ivykis, which would make me *very* happy.
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Unix Services, University Systems, University of Victoria
Evan Rempel <erempel@uvic.ca> writes:
I know Gergely Nagy is working very hard to get 3.3.6 out the door, but I wanted to add one more (easy) thing to the bug list for this release.
Bug 147 included the patterndb-4.xsd file into the source tarball, but it was not added to the doc/Makefile.in
I have attached a patch that fixes this.
Applied with a minor modification: patched Makefile.am instead of .in, as the former is the source of the latter. Thanks for the report & patch! -- |8]
participants (4)
-
Balazs Scheidler
-
Evan Rempel
-
Gergely Nagy
-
Gergely Nagy