Formerly:  ChipN@ingres.com
Paul Graves wrote:
> 
> Is there any consensus on how to manage errlog.log ?
> 
> In our development environment it just keeps growing and growing, till
> I decide to shutdown Ingres, rename it, and create a new empty file.
> This works fine at the moment.  Soon we start up the production
> environment and I need to be more organised.
> 
> I would like to split it up into one file per day, and archive/delete
> old files after 30 (?) days.  Does anyone do this with a running
> system ?  Will Ingres get upset if I start opening errlog.log and
> deleting records using a shell script or a C program ?
> 
-- 
Ingres only opens errlog.log when it tries to write to it.  I often edit
our file to reset error conditions that cause I/Watch to raise alarms. 
Our procedure is to rename the file and create a new one using the DG
agefile script.  My only concern is your error rate.  It must be
tremendous if you need to replace your errlog.log daily.

================================================================
Mike Mohr, Database Administrator === Email: Mike.Mohr@ait.ac.nz
Information Technology Group      === Phone: 64 9 307-9999 x8133
Auckland Institute of Technology  === Fax:   64 9 307-9901
PO Box 92006, Auckland, New Zealand = 
http://web.ait.ac.nz/homepages/staff/mmohr/
================================================================

Ingres Q & A

To William's Home Page

© William Yuan 2000

Email William