mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PTXdist klogd and syslogd
Date: Sun, 17 Nov 2013 20:18:18 +0100	[thread overview]
Message-ID: <20131117191818.GA31417@pengutronix.de> (raw)
In-Reply-To: <loom.20131030T091420-933@post.gmane.org>

Hi,

On Wed, Oct 30, 2013 at 08:28:36AM +0000, Dave wrote:
> When you select both Busybox syslogd and Busybox klogd you get the message
> "klogd should not be used together with syslog to kernel printk buffer".
> 
> At first I thought this meant you can't use both logging facilities at the
> same time.  However, PTXCONF_BUSYBOX_SYSLOGD help says "when used in
> conjunction with klogd ...
> 
> I would expect that if you could not use both at the same time then
> menuconfig would have the necessary rules to ensure that you didn't.
> 
> Would someone explain in more detail what that message is trying to convey?

I have no idea. The whole busybox configuration is just imported from the
busybox source tree. So you best bet is to ask busybox upstream about this.

> If you can use both together can you also use Busybox's klogd with inetutils
> syslogd?  (You don't get the "warning" message when you choose those two).

klogd just feeds the kernel messages into syslog. It should work, unless
the syslog daemon reads the kernel messages directly.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-11-17 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  8:28 Dave
2013-11-17 19:18 ` Michael Olbrich [this message]
2013-11-18  4:05   ` dave festing
2013-11-20 14:07 ` Jürgen Beisert
2013-11-21 13:26   ` Jürgen Beisert
2013-11-25  1:28     ` dave festing

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=20131117191818.GA31417@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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