public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Rsyslog: New advanced syslogger [TESTING]
Date: Mon, 09 Apr 2018 19:43:32 +0200	[thread overview]
Message-ID: <20180409194332.5351614b.peter.mueller@link38.eu> (raw)
In-Reply-To: <1523209643.5576.5.camel@ipfire.org>

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

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. :-\
> 
> Current DEV state can be found in here -->
> https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=ee0fc28e34f30fe687f4ab9c9130240d27dd87d4
> .
> 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...).
> 
> All the best,
> 
> Erik



  reply	other threads:[~2018-04-09 17:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1517906901-30146-1-git-send-email-erik.kapfer@ipfire.org>
2018-04-08 17:47 ` ummeegge
2018-04-09 17:43   ` Peter Müller [this message]
2018-04-10  9:29     ` ummeegge
2018-02-06  8:56 Erik Kapfer
2018-02-06  9:14 ` ummeegge
2018-02-13  6:26   ` ummeegge
2018-02-13 10:09     ` Michael Tremer
2018-02-13 12:41       ` ummeegge
2018-02-14 11:52         ` Michael Tremer
2018-02-14 14:17           ` ummeegge
2018-02-14 20:29             ` Michael Tremer
2018-02-27 12:38     ` ummeegge

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=20180409194332.5351614b.peter.mueller@link38.eu \
    --to=peter.mueller@link38.eu \
    --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