OpenCALEA
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: [OpenCALEA] Re: control design
- From: Ken Jenson
- Date: Thu Apr 05 13:59:58 2007
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=DhRfyZGnu3UgGtR16u6SYlkK0k4wi2ICUZtvum0lX20aEs4D9PgHhopkbO04i0q2QgTtb9075LmY0qQ1cZgBHBIZ95YS9lJSWHYUqvER5gslbl4meTYUJudUUo6jkjj72PHmmsaVY07zkDGC5aY7PaKw8cLU1VBX2PHd11ZKdcE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=USBlmeLlmSaXzJNscxf/AmmXxc7JXRGSgoBuXMYd3+0UDqD4YuSurgZcYThwQnGLW7I5ujGNDIRhWgb4rz01znno0DcG7U0U766T5EwqSgBCucqAEFKtEe9KNXKGcVXQ/avFmkynerhONiNyBEIHpk02xYqo+kGMR0iJ/fElzKI=
We are currently integrating a PHP application with a box running OpenCalea. We are creating php forms for Tap Config, Collector Config and Tap session management. We are writing a file that contains session information so that on reboot we can restart those sessions. All actions are via 'shell_exec' using command line parameters.
It would be nice to have some of the session management more automated. It would be nice to be able to easily query a list of tap sessions with their attributes, start an stop them etc. If the functions returned XML that would be sweet.
We are shipping next week so I guess some of my requests will need to wait until a couple of versions later.
I would love to see a LAMP wrapper, in fact, I wouldn't mind contributing something to it..
Ken Jenson
On 4/5/07, Rich <w7ki@northwestradio.com> wrote:
>>
>> Another option would be to define an "interception" in a database of
>> sorts (rdbms or otherwise), and have every IAP source independently
>> check that database periodically (frequently), and take appropriate
>> action (eg. start/restart/stop an intercept, and send CmII events).
>> There would still need to be an interface (possibly gui?) to define an
>> intercept, and if each data source logged info it could also be used as
>> part of the "secure and accurate record" we keep.
>>
>> Ideas for other options are certainly welcome.
Perhaps we could make a 'LAMP' wrapper such that we can retain the
simplicity of a command-line driven program while offering a GUI feature set
to those who are interested.
Also, FWIW, everything compiles & runs on a vanilla CentOS 4.4 install.
- Rich
--
Ken Jenson
801-224-6302 (hm)
801-318-1200 (cell)
|
