Request to replace sysklogd with rsyslog for 2.4
With 2.4, it'd be nice to move away from the older sysklogd to the newer rsyslog, which provides some useful new features over sysklogd, such as remote logging over TCP. In addition, it is also actively maintained (sysklogd technically is, but development is slow). It is also a drop-in replacement, so long as the patch in my former e-mail about moving syslog-daemon starting to init scripts is applied, as all that would be required is to put "rsyslog" the SERVICES array in /etc/rc.conf. It also has the nice side-effect here of working every time I rebuild it, which sysklogd 1.5 has given me much grief over (klogd either works fine or segfaults on start and I can't seem to pin down exactly why, I know it's not my memory though, I've ran it through memtest a number of times). -- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc
On Thu, 6 Sep 2007 21:31:31 -0400 Brett Goulder wrote:
With 2.4, it'd be nice to move away from the older sysklogd to the newer rsyslog, which provides some useful new features over sysklogd, such as remote logging over TCP. In addition, it is also actively maintained (sysklogd technically is, but development is slow). It is also a drop-in replacement, so long as the patch in my former e-mail about moving syslog-daemon starting to init scripts is applied, as all that would be required is to put "rsyslog" the SERVICES array in /etc/rc.conf.
It also has the nice side-effect here of working every time I rebuild it, which sysklogd 1.5 has given me much grief over (klogd either works fine or segfaults on start and I can't seem to pin down exactly why, I know it's not my memory though, I've ran it through memtest a number of times).
Sorry, I forgot to attach the rsyslog port tarball, here it is. -- ~predatorfreak GnuPG Public key: http://pred.dcaf-security.org/dcafsec-pub-gpgkey.asc
On Thu, Sep 06, 2007 at 09:31:31PM -0400, Brett Goulder wrote: Hi Brett,
With 2.4, it'd be nice to move away from the older sysklogd to the newer rsyslog, which provides some useful new features over sysklogd, such as remote logging over TCP. In addition, it is also actively maintained (sysklogd technically is, but development is slow). It is also a drop-in replacement, so long as the patch in my former e-mail about moving syslog-daemon starting to init scripts is applied, as all that would be required is to put "rsyslog" the SERVICES array in /etc/rc.conf.
Thanks for your suggestion and the port. TBH I don't see a real reason to switch to rsyslog. Sysklogd works fine since years and most people how need more functionality will use syslog-ng. If 1.5 has introduced a new bug, I'd downgrade to 1.4.1 until a fix is available.
It also has the nice side-effect here of working every time I rebuild it, which sysklogd 1.5 has given me much grief over (klogd either works fine or segfaults on start and I can't seem to pin down exactly why, I know it's not my memory though, I've ran it through memtest a number of times).
As already mentioned in my other mail, I'd suggest to debug your problem. If klogd segfaults it should be possible to get a gdb backtrace from the core-file, I'm pretty sure upstream will provide a fix if there's a bug in klogd. kind regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
participants (2)
-
Brett Goulder -
Juergen Daubert