No pidfile support in Argus 3.0?

[carter at qosient.com]

Hmmmmm, as I mentioned before this is working on linux and macos x, so there must be some kind of bug.  You are not setting anything related to pid generation in your argus.conf file?

The pid file name doesn't look arbitrary to me.

Carter

Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax  

-----Original Message-----
From: Andrew Pollock <andrew-argus at andrew.net.au>
Date: Mon, 24 Jul 2006 18:32:43 
To:Carter Bullard <carter at qosient.com>
Cc:argus-info at lists.andrew.cmu.edu
Subject: Re: [ARGUS] No pidfile support in Argus 3.0?

On Mon, Jul 10, 2006 at 10:49:14AM -0400, Carter Bullard wrote:
> Hey Andrew,
> There is pid file support in argus, at least there is suppose to be,
> and it is on by default.   On one of my mac's, argus created this
> lock file:
> 
>    /var/run/argus.en0.0.pid

I ran the daemon under strace and saw no mention of a pidfile. Also, if it's
going to use arbitrary interface names in the file, this makes it slightly
less predicatable for the purposes of an init script. The 2.0.6 init script
we were using in Debian explicitly named the PID file with the -n option
that no longer exists.
 
> So, in the clients I added a pid target directory option to the .rarc
> file, will we need that here?

I don't understand this statement.
 
> I moved the 'started' statement so that it has the daemon's pid
> if you use the '-d' or DAEMON option in the .conf file.
> 
> Any other issues?

Well at the moment, I don't have a good foundation for a reliable init
script, unless I'm missing something obvious.

regards

Andrew