X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88481.501C0184@onstor-exch02.onstor.net>; Wed, 12 Mar 2008 13:40:30 -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  TED00022685 Cougar - crontab doesn't have entries for newsyslog (so elogs not uploaded by emrs) WAD
Date: Wed, 12 Mar 2008 13:40:30 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08D2A692@onstor-exch02.onstor.net>
In-Reply-To: <20080312133148.7dc11857@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Defect  TED00022685 Cougar - crontab doesn't have entries for newsyslog (so elogs not uploaded by emrs) WAD
Thread-Index: AciEgBjCi97/uMwFSaaZaNrWn+WWPAAAOv4w
References: <ONSTOR-EXCH01s7szF7000022e0@onstor-exch01.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E08D2A24E@onstor-exch02.onstor.net><20080312110821.43a19884@ripper.onstor.net><9F7F8E8B-F5C2-41EF-87A7-638D4AE29E2E@onstor.com> <20080312133148.7dc11857@ripper.onstor.net>
From: "John Keiffer" <john.keiffer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Ian Brown" <ian.brown@onstor.com>
Cc: "Vikas Saini" <vikas.saini@onstor.com>,
	"Rendell Fong" <rendell.fong@onstor.com>


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=20
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/=20
> newsyslog.conf, which was initiated by the newsyslog entry in cron.  =20
> 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:
>=20
> Perhaps Ian can answer this one better than myself.
>=20
> On Tue, 11 Mar 2008 21:21:07 -0700 "John Keiffer"
> <john.keiffer@onstor.com> wrote:
>=20
> >
> > 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:
> >
>=20
