AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080429092131.40908a91@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<kumarv@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	BB375AF679D4A34E9CA8DFA650E2B04E09B2AD83@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 29 Apr 2008 09:21:42 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Kumar Vakacharla (HCL)" <kumarv@onstor.com>
Subject: Re: Defect  TED00022673 /var full on g5r204. log files are taking
 all the space.
Message-ID: <20080429092142.5f80b68a@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E09B2AD83@onstor-exch02.onstor.net>
References: <ONSTOR-EXCH01XqZAmN000001b0@onstor-exch01.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E099E16B0@onstor-exch02.onstor.net>
	<20080428134508.29f652d5@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E09B2AD83@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

nfx-tree/code/ssc-elog/syslog.conf.linux

     let's talk about this because I'm not sure that this is quite
     correct, but I wanted to hear your reasoning on these changes.

     OK, I just read your other comments, yes, let's sit down and
     figure out exactly what we want to go where.



On Mon, 28 Apr 2008 17:12:26 -0700 "Kumar Vakacharla (HCL)"
<kumarv@onstor.com> wrote:

> Andy, 
> 
>  
> 
> I have already updated the defect with this info. 
> 
>  
> 
> There is one more issue raised along with it which is 'kern.log
> messages are also going to /var/log/messages'. 
> 
>  
> 
> I have done the fix for this and please review it.
> 
> kumarv@compile2>p4 describe 29013
> 
> Change 29013 by perforce@kumarv-DEV on 2008/04/28 16:37:38 *pending*
> 
>  
> 
>         Partial fix for defect  TED00022673 /var full on g5r204.
> 
>         log files are taking all the space.(cougar)
> 
>  
> 
>         Fixed the issue of kernel messages going to /var/log/messages
> as reported in
> 
>         the defect. Also done similar changes for other logs.
> 
>  
> 
> Affected files ...
> 
>  
> 
> ... //depot/dev/nfx-tree/code/ssc-elog/syslog.conf.linux#2 edit
> 
> kumarv@compile2>
> 
> Client - kumarv-DEV
> 
> Path : /homes/kumarv/work/dev/nfx-tree/code/ssc-elog/syslog.conf.linux
> 
>  
> 
> But now after doing that change, I got a doubt whether we really
> require the log files /var/log/messages and /var/log/debug? Because
> the messages in these files are subset of messages in /var/log/syslog
> and other logs.
> 
> 
>  
> 
> ------------------------------------------------------
> 
> *.=debug;\                                        <-- all debug
> messages
> 
>     auth,authpriv.none;\
> 
>     news.none;mail.none -/var/log/debug                          
> 
> *.=info;*.=notice;*.=warn;\                       <-- all messages of
> priority info, notice and warning. 
> 
>     auth,authpriv.none;\                          
> 
>     cron,daemon.none;\                            
> 
>     mail,news.none;\                              
> 
>     local0,local1.none;\                          
> 
>     local2,local3.none;\                          
> 
>     local4,local5.none;\                          
> 
>     local6,local7.none       -/var/log/messages   
> 
> ------------------------------------------------------
> 
> Please clarify me. 
> 
>  
> 
> Thanks,
> 
> Kumar. 
> 
>  
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Monday, April 28, 2008 1:45 PM
> To: Kumar Vakacharla (HCL)
> Cc: Vikas Saini
> Subject: Re: Defect TED00022673 /var full on g5r204. log files are
> taking all the space.
> 
>  
> 
> 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. 
> 
nfx-tree/code/ssc-elog/syslog.conf.linux

     let's talk about this because I'm not sure that this is quite
     correct, but I wanted to hear your reasoning on these changes.

