X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8B9E3.D26424E0@onstor-exch02.onstor.net>; Mon, 19 May 2008 12:09:11 -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: please review 29277
Date: Mon, 19 May 2008 12:09:11 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E09624B08@onstor-exch02.onstor.net>
In-Reply-To: <20080519102118.1d9da2e9@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: please review 29277
Thread-Index: Aci51MBMX6tTDOvKSFG+r5ct84fvUgACoBXQ
From: "Rendell Fong" <rendell.fong@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Ok - I assume you've checked the output that's being generated for the
bogus printf fix.


-----Original Message-----
From: Andy Sharp=20
Sent: Monday, May 19, 2008 10:21 AM
To: Rendell Fong
Subject: please review 29277

Change 29277 by andys@ripper on 2008/05/16 13:41:03 *pending*

        TED00022685 - elogs not uploaded to ERMS on logrotate
       =20
        Remove the code for Linux that attempts to wait on logrotate
        because I suspect it's not working, and because it isn't needed.
        What are the chances that someone will fire an elog upload by
        hand at the exact mllisecond logrotate rotates the file at
6.25am?
        What are the chances anyone will care, since the first might
        have a problem, but then the log will immediately get uploaded
        by logrotate?  Zero to none.
       =20
        TED00023450 - EMRS is not uploading config file nightly
       =20
        Bogus printf syntax fixed.  Should have been broken on BSD as
        well but I guess no one noticed.
       =20
        reviewed by

Affected files ...

... //depot/dev/nfx-tree/code/ssc-support/emrscron#21 edit

