From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from bay0-omc4-s1.bay0.hotmail.com ([65.54.190.203]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1Vkkyz-0003Wl-St for ptxdist@pengutronix.de; Mon, 25 Nov 2013 02:29:03 +0100 Message-ID: From: dave festing Date: Mon, 25 Nov 2013 01:28:53 +0000 In-Reply-To: <201311211426.00325.jbe@pengutronix.de> References: , <201311201507.59437.jbe@pengutronix.de>, <201311211426.00325.jbe@pengutronix.de> MIME-Version: 1.0 Subject: Re: [ptxdist] PTXdist klogd and syslogd Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0346114075==" Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" --===============0346114075== Content-Type: multipart/alternative; boundary="_38481bc1-1663-46d3-a2f6-b46908d209b7_" --_38481bc1-1663-46d3-a2f6-b46908d209b7_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thank you for the elaboration. Cheers=2C Dave > From: jbe@pengutronix.de > To: ptxdist@pengutronix.de > Date: Thu=2C 21 Nov 2013 14:26:00 +0100 > CC: dave_festing@hotmail.com > Subject: Re: [ptxdist] PTXdist klogd and syslogd >=20 > Hi Dave=2C >=20 > On Wednesday 20 November 2013 15:07:59 J=FCrgen 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 prin= tk > > > buffer". > > > > > > At first I thought this meant you can't use both logging facilities a= t > > > the same time. However=2C PTXCONF_BUSYBOX_SYSLOGD help says "when us= ed 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 b= uffer <---- this one? [ ] Use the klogctl() interface > > > > This is because "Linux kernel printk buffer support" in 'syslogd' and > > 'klogd' do the same. >=20 > Ups=2C forget this description. They do not the same. This option just pu= ts the > logging data into the printk buffer. This would end in an endless loop. k= logd > grabs the data from the printk buffer=2C forwards it to the syslogd daemo= n=2C > which forwards it again into the printk buffer. That is why this warning = is > shown in the menu. >=20 > If you want kernel messages in your logs=2C you need the klogd. >=20 > jbe >=20 > --=20 > Pengutronix e.K. | Juergen Beisert = | > Linux Solutions for Science and Industry | http://www.pengutronix.de= / | >=20 > --=20 > ptxdist mailing list > ptxdist@pengutronix.de = --_38481bc1-1663-46d3-a2f6-b46908d209b7_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Thank you for the elaboration.
Cheers=2C
Dave

>=3B From: jbe@pengutronix.de
>= =3B To: ptxdist@pengutronix.de
>=3B Date: Thu=2C 21 Nov 2013 14:26:00 = +0100
>=3B CC: dave_festing@hotmail.com
>=3B Subject: Re: [ptxdis= t] PTXdist klogd and syslogd
>=3B
>=3B Hi Dave=2C
>=3B
= >=3B On Wednesday 20 November 2013 15:07:59 J=FCrgen Beisert wrote:
&g= t=3B >=3B On Wednesday 30 October 2013 09:28:36 Dave wrote:
>=3B >= =3B >=3B When you select both Busybox syslogd and Busybox klogd you get t= he
>=3B >=3B >=3B message "klogd should not be used together with = syslog to kernel printk
>=3B >=3B >=3B buffer".
>=3B >=3B &= gt=3B
>=3B >=3B >=3B At first I thought this meant you can't use b= oth logging facilities at
>=3B >=3B >=3B the same time. However= =2C PTXCONF_BUSYBOX_SYSLOGD help says "when used in
>=3B >=3B >=3B= conjunction with klogd ...
>=3B >=3B >=3B
>=3B >=3B >=3B= I would expect that if you could not use both at the same time then
>= =3B >=3B >=3B menuconfig would have the necessary rules to ensure that = you didn't.
>=3B >=3B >=3B
>=3B >=3B >=3B Would someone e= xplain in more detail what that message is trying to
>=3B >=3B >= =3B convey?
>=3B >=3B
>=3B >=3B You mean this message in the = menuconfig?
>=3B >=3B
>=3B >=3B [*] syslogd
>=3B >=3B= [....]
>=3B >=3B [*] Linux kernel printk buffer support
&g= t=3B >=3B [*] klogd
>=3B >=3B --- klogd should not be used tog= ether with syslog to kernel printk buffer <=3B---- this one? [ ] Use th= e klogctl() interface
>=3B >=3B
>=3B >=3B This is because "Li= nux kernel printk buffer support" in 'syslogd' and
>=3B >=3B 'klogd'= do the same.
>=3B
>=3B Ups=2C forget this description. They do = not the same. This option just puts the
>=3B logging data into the pri= ntk buffer. This would end in an endless loop. klogd
>=3B grabs the da= ta from the printk buffer=2C forwards it to the syslogd daemon=2C
>=3B= which forwards it again into the printk buffer. That is why this warning i= s
>=3B shown in the menu.
>=3B
>=3B If you want kernel mess= ages in your logs=2C you need the klogd.
>=3B
>=3B jbe
>=3B=
>=3B --
>=3B Pengutronix e.K. =3B =3B =3B = =3B =3B =3B =3B =3B =3B =3B =3B =3B= =3B =3B =3B| Juergen Beisert =3B =3B =3B &nb= sp=3B =3B =3B |
>=3B Linux Solutions for Science and Industr= y =3B =3B =3B| http://www.pengutronix.de/ |
>=3B
&= gt=3B --
>=3B ptxdist mailing list
>=3B ptxdist@pengutronix.de

= --_38481bc1-1663-46d3-a2f6-b46908d209b7_-- --===============0346114075== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ptxdist mailing list ptxdist@pengutronix.de --===============0346114075==--