public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing Core Update 118
Date: Thu, 01 Feb 2018 15:43:54 +0100	[thread overview]
Message-ID: <8E147F50-C1BB-4152-8098-107F1FF8E8BD@ipfire.org> (raw)
In-Reply-To: <1517485049.21272.21.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

Hello,

Am 01.02.2018 um 12:37 schrieb Michael Tremer:

> Hi,
> 
> nothing of that sounds too bad - except that it sounds a bit extortionate for
> just some syslogging.
> 
> Maybe it is worth trying it if can be built without json at least.

Have tried yesterday for fast checkout if it builds but the compilation quits causing a non existing libfastjson. Also the Rsyslog documentation points json-c as a requirement --> http://www.rsyslog.com/doc/master/installation/install_from_source.html#build-requirements out, not sure if can get around it . Some of the other listed libs at the bottom might not be a requirement but possibly a nice one to have even the logs should be send to a remote log server.
Rsyslog do provides really a lot of extensions which might be worth for a look over...

> 
> However, since we are on the topic of logging reliably, it might be interesting
> to have support for SSL in there.

This should be no problem i think. Rsyslog can be linked against libgcrypt, GnuTLS and OpenSSL. A build is currently running on a openssl-11 basis whereby i think OpenSSL should be preferred ?

> 
> Have you tried if the old configuration file works or does it come with a new
> configuration file format?

The new version 8.32 is in building process will check this if it is ready. On my first tries with Rsyslog which is no also 1+ year ago, i needed to make two changes on syslog.conf --> https://forum.ipfire.org/viewtopic.php?t=16669#p98481 and after that i renamed it to rsyslog.conf and everything worked just fine.

> 
> Best,
> -Michael
> 
> On Thu, 2018-02-01 at 09:41 +0100, ummeegge wrote:
>> Hi all,
>> 
>> Am 31.01.2018 um 17:35 schrieb Michael Tremer:
>> 
>>> I wouldn't mind changing to rsyslog, but would this be just a drop-in
>>> replacement or cause some serious work?
>> 
>> longer time ago i have integrated Rsyslog into IPFire --> https://forum.ipfire
>> .org/viewtopic.php?t=16669 which was not that difficult but there was the need
>> for some new packages. As far as i remember i worked there with
>> 
>> libtasn1
>> libestr
>> json-c
>> liblogging
>> libfastjson
>> librelp
>> 
>> as a beneath info.
>> 
>>> 
>>> -Michael
>> 
>> 
>> Greetings,
>> 
>> Erik


  reply	other threads:[~2018-02-01 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1517416528.2586.92.camel@ipfire.org>
2018-02-01  8:41 ` ummeegge
2018-02-01 11:37   ` Michael Tremer
2018-02-01 14:43     ` ummeegge [this message]
2018-02-01 15:16       ` Michael Tremer
2018-02-02 19:49         ` ummeegge
2018-02-03 19:42           ` ummeegge
2018-02-06  9:37         ` ummeegge
2018-02-06 16:30           ` Michael Tremer
2018-01-30 17:44 Peter Müller
2018-01-30 20:57 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8E147F50-C1BB-4152-8098-107F1FF8E8BD@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox