* [ptxdist] PTXdist klogd and syslogd
@ 2013-10-30 8:28 Dave
2013-11-17 19:18 ` Michael Olbrich
2013-11-20 14:07 ` Jürgen Beisert
0 siblings, 2 replies; 6+ messages in thread
From: Dave @ 2013-10-30 8:28 UTC (permalink / raw)
To: ptxdist
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?
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).
Thanks,
Dave
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ptxdist] PTXdist klogd and syslogd
2013-10-30 8:28 [ptxdist] PTXdist klogd and syslogd Dave
@ 2013-11-17 19:18 ` Michael Olbrich
2013-11-18 4:05 ` dave festing
2013-11-20 14:07 ` Jürgen Beisert
1 sibling, 1 reply; 6+ messages in thread
From: Michael Olbrich @ 2013-11-17 19:18 UTC (permalink / raw)
To: ptxdist
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ptxdist] PTXdist klogd and syslogd
2013-11-17 19:18 ` Michael Olbrich
@ 2013-11-18 4:05 ` dave festing
0 siblings, 0 replies; 6+ messages in thread
From: dave festing @ 2013-11-18 4:05 UTC (permalink / raw)
To: ptxdist
[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]
Thank you.
Dave
> Date: Sun, 17 Nov 2013 20:18:18 +0100
> From: m.olbrich@pengutronix.de
> To: ptxdist@pengutronix.de
> Subject: Re: [ptxdist] PTXdist klogd and syslogd
>
> 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
[-- Attachment #1.2: Type: text/html, Size: 2186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ptxdist] PTXdist klogd and syslogd
2013-10-30 8:28 [ptxdist] PTXdist klogd and syslogd Dave
2013-11-17 19:18 ` Michael Olbrich
@ 2013-11-20 14:07 ` Jürgen Beisert
2013-11-21 13:26 ` Jürgen Beisert
1 sibling, 1 reply; 6+ messages in thread
From: Jürgen Beisert @ 2013-11-20 14:07 UTC (permalink / raw)
To: ptxdist; +Cc: Dave
Hi Dave,
I just stumbled about the same menu entry.
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.
You should disable 'klogd' or 'syslogd's "Linux kernel printk buffer support".
If you do so the menu changes to:
[*] syslogd
[....]
[ ] Linux kernel printk buffer support
[*] klogd
[ ] Use the klogctl() interface
Or:
[*] syslogd
[....]
[*] Linux kernel printk buffer support
[ ] klogd
And everything should be fine.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ptxdist] PTXdist klogd and syslogd
2013-11-20 14:07 ` Jürgen Beisert
@ 2013-11-21 13:26 ` Jürgen Beisert
2013-11-25 1:28 ` dave festing
0 siblings, 1 reply; 6+ messages in thread
From: Jürgen Beisert @ 2013-11-21 13:26 UTC (permalink / raw)
To: ptxdist; +Cc: Dave
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [ptxdist] PTXdist klogd and syslogd
2013-11-21 13:26 ` Jürgen Beisert
@ 2013-11-25 1:28 ` dave festing
0 siblings, 0 replies; 6+ messages in thread
From: dave festing @ 2013-11-25 1:28 UTC (permalink / raw)
To: ptxdist
[-- 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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-11-25 1:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-30 8:28 [ptxdist] PTXdist klogd and syslogd 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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox