AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080428134453.1ce97935@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<kumarv@onstor.com>,<vikas.saini@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E099E16B0@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 28 Apr 2008 13:45:08 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Kumar Vakacharla (HCL)" <kumarv@onstor.com>
Cc: "Vikas Saini" <vikas.saini@onstor.com>
Subject: Re: Defect  TED00022673 /var full on g5r204. log files are taking
 all the space.
Message-ID: <20080428134508.29f652d5@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E099E16B0@onstor-exch02.onstor.net>
References: <ONSTOR-EXCH01XqZAmN000001b0@onstor-exch01.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E099E16B0@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Kumar,

Paste this info into the bug and move onto something else, as I believe
we will want to fine tune this, but it doesn't rise to the level of a
BMF, unless there is something else I'm not aware of.

Cheers,

a


On Mon, 28 Apr 2008 11:15:33 -0700 "Kumar Vakacharla (HCL)"
<kumarv@onstor.com> wrote:

> Andy, 
> 
> I require your inputs on the following concern raised by Vikas
> regarding messages in kern.log ...
> 
> He says: 
> >>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.*).  
> Klogd service traps all the messages that are printed to the consoles
> (by reading /proc/kmsg file). 
> 
> 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. 
> 
> Shall we need to really stop this behavior in our box? 
> 
> Please provide me your inputs regarding this. 
> 
> 
> Thanks,
> Kumar. 
