Argus 2.0 wishes

[Carter Bullard]

Hey Peter,
   We can implement your suggestion with Neil's approach.
Maintaining internal argus state is indeed really
important.  As long as the configuration file hasn't
changed when we get the SIGINT, then we don't have to
reinitialize the Argus.  We can switch files, but I'd
like to hear more justification for flushing all the
records.

Carter

   

> -----Original Message-----
> From: Peter Van Epp [mailto:vanepp at sfu.ca]
> Sent: Thursday, March 16, 2000 11:22 AM
> To: argus at lists.andrew.cmu.edu
> Subject: Re: Argus 2.0 wishes
> 
> 
> 	The discussion on signals jogged my mind for another 
> request (which
> fits in with the config file). I'd like a signal that will 
> switch log files.
> When the signal hits, argus flushes all the open flows to the 
> current log 
> file (but keeps the current state in memory still) as if it 
> had sigHUPed,
> writes the terminate record, closes the file and opens a new 
> one (file name 
> created from parameters in the argus config file) and 
> continues on without
> really shutting down. I'm working on something like that 
> (slowly!) externally
>  with the shadow startup perl scripts, but internal to argus 
> would be even 
> better because of not loosing current active state from shutdowns. 
> 
> Peter Van Epp / Operations and Technical Support 
> Simon Fraser University, Burnaby, B.C. Canada
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20000316/b7d4d7af/attachment.html>