Re: Testing Core Update 118

[Michael Tremer <michael.tremer@ipfire.org>]

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

Hi,

On Thu, 2018-02-01 at 15:43 +0100, ummeegge wrote:
> 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...

I am not sure if we need any of the extensions since we are basically
using the bare minimum at the moment - sysklogd cannot do much more.
And so far nobody has really complained about this.

json-c is fine. Some other packages need this too and I am sure that I
have built this before somewhere.

The rest: I think the rsyslogd people are doing this a bit wrong. It is
quite an excessive amount of libraries and I do not get why some basic
functionality like a syslog daemon needs that. But I guess we don't
have any other choice here than packaging all of them.

> > 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 ?

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.

That sounds good. They have their own configuration file format for
some modules stuff but since we don't intend to use any of that, we
should be fine here.

Would you update those packages and rebase the branch on next since you
have already been working on this? Please send this over to Peter for
review then and let him test the TCP logging capabilities since he was
the one who required this in the first place.

But let's only start working on this when the current OpenVPN stuff is
done.

Best,
-Michael

> 
> > 
> > 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
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]