pid file

[Carter Bullard]

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?

# would be a unique index.

I currently have an 'ARGUS_SET_PID=' variable in the
.argusrc file, so you can tell argus whether to
create a pid file or not.  This should allow you
to have one "critical" instance set a pid file, so
you can test whether its still running or not
from a cron job.  Other, temporary, argi would
not need to put down a pid.  I thought that this
would avoid collision problems with multiple argi.

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: Tuesday, December 19, 2000 10:19 PM
To: argus
Subject: Re: pid file


>
> Gentle people,
>    So I've put pid file support into "J", which should be on the
> server late this afternoon.  There are a number of issues with
> this support, so I would love some comments.
>

	OK :-) when I ripped off the Shadow perl scripts to start argus this
issue came up. They solve it by having an instance name for the task (which
is of course easier when you are launching a program from perl than internal
to argus). I'd like to see a way of keeping that (because I sometimes do run
more than one argus although not usually on the same interface). Perhaps yet
another command line argument to set an instance name (which will cause a
pid file of the form "instance_name.pid" instead of the default "argus.pid"
or something similar?)  for those of us wanting to do odd things?

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/2881ae17/attachment.html>