argusarchive.

[Carter Bullard]

Hey Scott,
   Yes I found a set of problems relating to writing out
queued records when the file has been removed.  I've
fixed them in the 2.0.4 code that is in the test directory.

ftp://qosient.com/dev/argus-2.0/argus-2.0.4.beta.1.tar.gz

Could you give this a try?

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 588-9133
Fax   +1 212 588-9134
http://qosient.com

> -----Original Message-----
> From: owner-argus-info at lists.andrew.cmu.edu 
> [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of 
> Scott A. McIntyre
> Sent: Thursday, November 01, 2001 2:26 PM
> To: Carter Bullard
> Cc: 'Argus Mailing List'
> Subject: Re: argusarchive.
> 
> 
> > If the output file is gone, we will close it, and
> > reestablish the output file, swap the file
> > descriptors and be on our way, but there must be
> > something nefarious going on.  With the stack looking corrupted, we 
> > may have lost a pointer or an index number, so ....  let me take a 
> > look around.
> 
> I just thought of something else which may be a contributing 
> factor, but shouldn't be -- the filesystem is XFS.
> 
> Not sure if that will weigh in your considerations, but it 
> seems possible that there could be an interaction between the 
> journalling and other features of XFS as implemented on 
> Linux, and what's going on.
> 
> However, this is not the first Linux/XFS system I've run 
> Argus on, so this may mean nothing.
> 
> 
> 
>