pid file

Carter Bullard carter at qosient.com
Wed Dec 20 23:19:14 EST 2000


Gentle people,
Fair enough.  Seems like we'll go with

    basename.interface.#.pid

The first # will be 0.
It should be in tomorrow's upload.  I'll still
leave in the ARGUS_SET_PID= variable if
someone wants to control it a bit.

Carter

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

carter at qosient.com
Phone +1 212 813-9426
Fax   +1 212 813-9426


-----Original Message-----
From: owner-argus at lists.andrew.cmu.edu
[mailto:owner-argus at lists.andrew.cmu.edu]On Behalf Of Peter Van Epp
Sent: Wednesday, December 20, 2000 11:14 PM
To: argus
Subject: Re: RE: pid file


> 
> 
> On Wed, 20 Dec 2000 12:17:38 -0500 Carter Bullard <carter at qosient.com> 
> wrote:
> 
> > Hey Peter,
> >    So what would be a good candidate for
> > "instance_name"?  I could do something like,
> > 
> >    basename.interface.#.pid
> > 
> > Problem is that one argus can read from multiple
> > interfaces, so which interface do we put in?
> >
> 
> First one listed (either on the command line or in the rc file?
> 
>  
> Russell Fulton, Computer and Network Security Officer
> The University of Auckland,  New Zealand
> 

	I was just about to suggest the same thing. Presumably in the cases
where you are using two interfaces (usually for full duplex I'd assume) you
will know which interfaces are part of the group from having at least one 
specified (and hopefully your basename will tell you what the link is even
without the interface ...).

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/20001220/c6f3247d/attachment.html>


More information about the argus mailing list