changes to /cgi-ipbin/ scripts

Date: Wed, 8 Dec 1999 10:45:06 -0400 (AST)
From: Christopher Majka <nextug@is.dal.ca>
To: Michael Smith <michael@csuite.ns.ca>
cc: CCN Information Provider Committee <ccn-ip@chebucto.ns.ca>, CCN Technical Committee <ccn-tech@chebucto.ns.ca>
Precedence: bulk
Return-Path: <ccn-ip-mml-owner@chebucto.ns.ca>

next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects

Index of Subjects
This suggestion dates back some three years and is based on correspondence
that David Trueman and I had about the IPDB. Here is the salient
communication:

On Sat, 7 Dec 1996, David Trueman wrote:

> These are good ideas and should be implemented. Right now, I can't say
> when but it will at least be on record in the archive, now.  You might
> want to remind us in early January.

O.K. Shall do. Its good to at least have it in the 'in' tray!  :-)

>> I would be great if there was a script of some sort that on a periodic
>> basis checked the IPDB.
>>
>> 1) For non-active applications it would check to see the last time there
>> had been a change in the status of the application. If that was > 1 year
>> it would send some sort of succinct message to ccn-ip reporting this
>> condition.
>>
>> [Comment: thus an alert to us of Applications that had gone dormant,
>> we could either work to activate them up or close them down.]
>>
>> 2) For active IPs it would check the list of IPEs and ascertain that
>> there was at least one with an active CCN user account. If the entry
>> failed this criterion, again some succinct message would be sent to
>>ccn-ip informing us of this situation.
>>
>> [Comment: thus we could take action on such problem areas].

These would be useful tools in terms of having at least a minimal level of
background monitoring of our IPs. Having gone through the entire IP
Database I can attest to (even with our current number of IP's) how much
work this is. As we grow there will be no realistic way to monitor 'dead'
applications and 'orphaned' IPs otherwise.

We need to be able to be:

a) relatively confident of the information we have in the IPDB; and

b) build on the functionality that is there.

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I'm would be great to add such tools which would allow the IP Committee to
better monitor and administer our IPs. I hope that we can implement the
above ideas. Comments?

Cheers!

Chris

_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.
Christopher Majka                               <aa051@chebucto.ns.ca>
Editor-in-Chief: Chebucto Community Net - Halifax, Nova Scotia, Canada
URL = http://www.chebucto.ns.ca/Home.html
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._.


next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects