From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: [PATCH] Rsyslog: New advanced syslogger [TESTING] Date: Mon, 09 Apr 2018 19:43:32 +0200 Message-ID: <20180409194332.5351614b.peter.mueller@link38.eu> In-Reply-To: <1523209643.5576.5.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3127209242131368447==" List-Id: --===============3127209242131368447== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Erik, thanks for working on this and sorry for the late reply. > Hi all, > after some testing rounds in this topic am currently arrived at a more > simple configuration (without GnuTLS, Kerberos, ...) which works for me > without problems also with the already integrated config.dat WUI > extension for TCP protocols. Thanks again. Support for those protocols is not that important in my point of view, since I never saw anybody using SSL or similar for syslogging. In fact, most "enterprise" software (which is enterprisely sophisticated) does not even support TCP. :-\ >=20 > Current DEV state can be found in here --> > https://git.ipfire.org/?p=3Dpeople/ummeegge/ipfire-2.x.git;a=3Dcommit;h=3De= e0fc28e34f30fe687f4ab9c9130240d27dd87d4 > . > A question arises for me now, should we substitute Sysklogd and Klogd > with Rsyslog now ? If yes, how should we proceed further then ? I think so, if there are no issues left. Will try and test (might take a while, since things are busy here...). >=20 > All the best, >=20 > Erik --===============3127209242131368447==--