AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080313105358.259616c4@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.keiffer@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	BB375AF679D4A34E9CA8DFA650E2B04E08D2A6EB@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 13 Mar 2008 10:56:41 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Keiffer" <john.keiffer@onstor.com>
Subject: Re: Defect  TED00022685 Cougar - crontab doesn't have entries for
 newsyslog (so elogs not uploaded by emrs) WAD
Message-ID: <20080313105641.03857155@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08D2A6EB@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E08D2A6EB@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

Sorry, got sidetracked several times when I went to go track this
down.  I do mean Kumar ~:^)

Bug would not be obvious to find.  It is

TED00021741 [Cougar] user with CLUSTER,SECURITY in clustesr priveleges cannot find or view elog messages


On Wed, 12 Mar 2008 14:07:36 -0700 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> 
> Do you mean "Kumaravel Palanisamy" or someone else? I searched CQ and
> cannot find any defect that sounds the same as mine. (I only searched
> on elogs, logs, and EMRS though...)
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Wednesday, March 12, 2008 1:43 PM
> To: John Keiffer
> Cc: Ian Brown; Vikas Saini; Rendell Fong
> Subject: Re: Defect TED00022685 Cougar - crontab doesn't have entries
> for newsyslog (so elogs not uploaded by emrs) WAD
> 
> There is a defect.  Kumar is working on it.
> 
> On Wed, 12 Mar 2008 13:40:30 -0700 "John Keiffer"
> <john.keiffer@onstor.com> wrote:
> 
> > 
> > Is there a defect for that pending fix? The intention of my defect
> > was to ensure that elogs are uploaded to the DW. It sound like
> > maybe my description should be changed, and if I did change it then
> > this defect is either NOT a WAD or it is a Duplicate of the one you
> > are describing...
> > 
> > -John
> > 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Wednesday, March 12, 2008 1:32 PM
> > To: Ian Brown
> > Cc: John Keiffer; Vikas Saini; Rendell Fong
> > Subject: Re: Defect TED00022685 Cougar - crontab doesn't have
> > entries for newsyslog (so elogs not uploaded by emrs) WAD
> > 
> > On Wed, 12 Mar 2008 12:54:34 -0700 Ian Brown <ian.brown@onstor.com>
> > wrote:
> > 
> > > on bobcat, elog.0.gz file upload was kicked off by the /etc/ 
> > > newsyslog.conf, which was initiated by the newsyslog entry in
> > > cron. On cougar: that's your call.
> > 
> > If you're talking about "/onstor/bin/emrscron -s elog0 &" in the
> > newsyslog.conf file, then we have that in cougar, in the logrotate
> > config /etc/logrotate.d/onstor.
> > 
> > There is currently an outstanding bug that is causing this to fail,
> > however.  The fix is in the pipeline.
> > 
> > > On Mar 12, 2008, at 11:08 AM, Andrew Sharp wrote:
> > > 
> > > Perhaps Ian can answer this one better than myself.
> > > 
> > > On Tue, 11 Mar 2008 21:21:07 -0700 "John Keiffer"
> > > <john.keiffer@onstor.com> wrote:
> > > 
> > > >
> > > > Andy,
> > > >
> > > > What cron process will be in charge of uploading elogs though?
> > > > As far as I can tell, on Cougar, they currently won't be
> > > > uploaded.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > -----Original Message-----
> > > > From: andy.sharp@onstor.com [mailto:andy.sharp@onstor.com]
> > > > Sent: Tuesday, March 11, 2008 5:19 PM
> > > > To: John Keiffer; John Keiffer
> > > > Cc: Ian Brown; Andy Sharp; Vikas Saini; Rendell Fong; Andy Sharp
> > > > Subject: Defect TED00022685 Cougar - crontab doesn't have
> > > > entries for newsyslog (so elogs not uploaded by emrs) WAD
> > > >
> > > > Note_Entry: There's nothing in my Bobcat/BSD crontab that would
> > > > affect elog
> > > > operation.  On Cougar, all the emrscron entries are there that
> > > > need to be, and the rest of the entries in Bobcat/BSD crontab
> > > > are OpenBSD dist specific and not applicable to Cougar.
> > > > Files_list_entry:
> > > > Project:
> > > >
> > > 
