Re: old ClamAV databases and other antiques

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: old ClamAV databases and other antiques

Weir, Jason-2
Re: old ClamAV databases and other antiques

Robert,

Could I get a copy of the perl scripts (stats and greylist) that were housed on the sourceforge site, I might be able to house them somewhere they can be used..

Jason Weir
Systems Administrator
New Hampshire Retirement System
Concord, NH 03301
(603)-410-3634

Original Message:

I just got a warning about bandwidth mis-usage on the assp.sourceforge.net project home page. This was caused by the downloads for the old ClamAV virus database files. Since Virus-Scanning was completely rebuilt by 1.2.5, the files are not needed anymore. They are useless anyway, since they are from mid of July and thus completely outdated. I opt for deleting them from the project web alltogether. We have still another old feature that is not used but violating the sourceforge "acceptable use" policy: the greylist. The ASSP does still include the down- and upload routines, but the list is no more compiled at the site home. The greylist information is thus outdated too, even if the user tries its best to keep the list actual and repeatedly fetches the online version. I could offer webspace and bandwidth, but I currently have no possibility to run cron jobs on that web. Perhaps we should make an effort to relaunch the "ASSP application web" off the sourcforge "project web" since the latter one must not be used to offer "services" like the greylist compilation for the running ASSP installations. We could revive the greylist and "combined statistics" features when ASSP would not fetch the final files or uploads directly to the assp.sourceforge.net web, but instead fetches a short list of mirrors that would keep the list. However, we could cancel the feature to up- and download files periodically to comply with the sourceforge policy. Btw, the files on the sourceforge CVS are outdated even longer. They have not been updated since 1.2.2 beta over a year ago. While Fritz Borgstedt does a great job of driving ASSP development, he keeps the source local. However users keep downloading ancient CVS snapshots, as they rightfully assume this would be the most current development state. If nobody complains, I will upload a recent source to the CVS, even if it is not used for actual development. Best regards, Robert Orso




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/assp-devel
Reply | Threaded
Open this post in threaded view
|

Re: old ClamAV databases and other antiques

Robert Orso
That would be agreat idea, however we really should discuss, how such a
service should be handled in the future. Maybe we need to provide means
to configure ASSP to upload to a chosen site, in case it has to be
hosted some where else again. How to notify the existing installations?
It certainly would not be the best solution to host the function
"somewhere" i.e. a site that is not directly related to ASSP and code
the destination into the PERL source.

These functions are out of order for some time now without great impact
to the performance, so we do not have the pressure to restore some vital
functionality. Restoring this services should go hand in hand with a
solid redesign of the application home-site. The "stats" script would
provide only some very basic numbers that were available from the start.
The current statistical analysis is already far beyond that and it does
need a complete rewrite of the database structure and consolidation
scripts to keep up with that.

Currently we have a Sourceforge "home page" and various private support
webs. Development is not currently done with Sourceforge tools and the
project tends to roam around a little. The ideal solution would be a
true "assp-only" web site, completely owned by "the project" or at least
"completely dedicated" to it, so when things may change in the future,
the application site will still be in operation. So probably we either
have to raise funds for such a site, find someone who donates one or
start making (a little) money to finance centralized services.

The key point is to have the services hosted on a server that does not
get us in conflict with the usage policy (Sourceforge) and that does not
have to stretch the mercy of a single person too much.

The scripts by them self are pretty short and not complicated. Since the
current mySQL database does not seem to contain any values and the new
home would need different setup anyway, I removed the access parameters
from the scripts in the attachment, because they have to be passed
through the internet unsecured.

Best regards,
Robert

Weir, Jason schrieb:

>
> Robert,
>
> Could I get a copy of the perl scripts (stats and greylist) that were
> housed on the sourceforge site, I might be able to house them
> somewhere they can be used..
>
> Jason Weir
> Systems Administrator
> New Hampshire Retirement System
> Concord, NH 03301
> (603)-410-3634
>
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/assp-devel

obsolete.rar (7K) Download Attachment