X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8A95B.DA01BBB0@onstor-exch02.onstor.net>; Mon, 28 Apr 2008 11:15:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: Defect  TED00022673 /var full on g5r204. log files are taking all the space.
Date: Mon, 28 Apr 2008 11:15:33 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E099E16B0@onstor-exch02.onstor.net>
In-Reply-To: <ONSTOR-EXCH01XqZAmN000001b0@onstor-exch01.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00022673 /var full on g5r204. log files are taking all the space.
Thread-Index: AcinCUu+giHZJ1eASEW6/7d+0dqBnwCS9jiw
References: <ONSTOR-EXCH01XqZAmN000001b0@onstor-exch01.onstor.net>
From: "Kumar Vakacharla (HCL)" <kumarv@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Vikas Saini" <vikas.saini@onstor.com>

Andy,=20

I require your inputs on the following concern raised by Vikas regarding
messages in kern.log ...

He says:=20
>>if you look at contents in /var/log/kern.log...you will see all the
>>messages related to snapshot,ndmp, mirror or discovery of system. so i
>>don't think they are really kernel messages.

As per my understanding, In linux we have a service called klogd in
addition to default syslogd. This klogd is responsible for trapping all
kernel messages and direct them to syslogd and then syslogd redirects
them to the appropriate log files as per "syslog.conf" settings.
(kern.*). =20
Klogd service traps all the messages that are printed to the consoles
(by reading /proc/kmsg file).=20

If we have elog display enabled, all the elog messages in fp and txrx
will also get printed to their consoles. Hence they will be captured by
klogd and appears in kern.log file eventually. I believe Vikas has seen
this case and worrying about them. Also, there are some printf
statements in the code which always comes to kern.log irrespective of
elog display settings.=20

Shall we need to really stop this behavior in our box?=20

Please provide me your inputs regarding this.=20


Thanks,
Kumar.=20
