From: dave festing <dave_festing@hotmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] PTXdist klogd and syslogd
Date: Mon, 25 Nov 2013 01:28:53 +0000 [thread overview]
Message-ID: <BAY176-W2435319A345589BEF82071E2ED0@phx.gbl> (raw)
In-Reply-To: <201311211426.00325.jbe@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2056 bytes --]
Thank you for the elaboration.
Cheers,
Dave
> From: jbe@pengutronix.de
> To: ptxdist@pengutronix.de
> Date: Thu, 21 Nov 2013 14:26:00 +0100
> CC: dave_festing@hotmail.com
> Subject: Re: [ptxdist] PTXdist klogd and syslogd
>
> Hi Dave,
>
> On Wednesday 20 November 2013 15:07:59 Jürgen Beisert wrote:
> > On Wednesday 30 October 2013 09:28:36 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?
> >
> > You mean this message in the menuconfig?
> >
> > [*] syslogd
> > [....]
> > [*] Linux kernel printk buffer support
> > [*] klogd
> > --- klogd should not be used together with syslog to kernel printk buffer <---- this one? [ ] Use the klogctl() interface
> >
> > This is because "Linux kernel printk buffer support" in 'syslogd' and
> > 'klogd' do the same.
>
> Ups, forget this description. They do not the same. This option just puts the
> logging data into the printk buffer. This would end in an endless loop. klogd
> grabs the data from the printk buffer, forwards it to the syslogd daemon,
> which forwards it again into the printk buffer. That is why this warning is
> shown in the menu.
>
> If you want kernel messages in your logs, you need the klogd.
>
> jbe
>
> --
> Pengutronix e.K. | Juergen Beisert |
> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
[-- Attachment #1.2: Type: text/html, Size: 2791 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-11-25 1:29 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
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 [this message]
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=BAY176-W2435319A345589BEF82071E2ED0@phx.gbl \
--to=dave_festing@hotmail.com \
--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