This mail is an automated notification from the task tracker
of the project: Administration.
/**************************************************************************/
[task #119] Latest Modifications:
Changes by:
Mathieu Roy <[EMAIL PROTECTED]>
'Date:
sam 08.05.2004 � 20:00 (Europe/Paris)
------------------ Additional Follow-up Comments ----------------------------
No, it is not complex to set up webalizer. However, we need to make apache saving
logs for each area in separate files. That's not a big task either, that's doable. But
it still need to be done.
You are right, what would be need in a minimal script that create a webalizer conf
(hum, it may even not be necessary. Just one conffile + command line args may be
enough).
The robot.txt blocking access to search engines is a good idea, indeed.
However, a script handling webalizer conf creation should not touch cron. There should
be only one cron entry. Otherwise it would not be scalable.
--
How I understand your script, it would be called by the script that create the
homepage area at http://home.gna.org
--
The prefered language is Perl, as all the others scripts are in Perl.
The scripts must be in "use strict;" and should use "use Getopt::Long;" for command
line arguments.
--
The best is to have a script that takes as argument on the command line:
--conffile= path to the configuration file like /var/webalizer/group.conf
--logfile= path the apache log, like /var/log/apache/bygroup/group.log
--outputdir= path to the output directory for webalizer
like /var/www/group/webalizer/
--title= title for the webalizer results
It would be easy then to adapt the script homepage-update.pl to call that script.
No other group info other than the system name is available. The home.gna.org system
in a chroot that have no access to the database or anything else.
--
Another script (a trivial one) like homepage-update.pl should be written to run
webalizer on each conffile, and that script will be run via cron. In fact,
homepage-update.pl would only need very trivial changes for that.
--
So if you can write the first script, it would be easy for us to include it in our
bunch of scripts.
If you want, we can give you write access to the cvs repository, which is not public
(but all the code is GPL).
/**************************************************************************/
[task #119] Full Item Snapshot:
URL: <http://gna.org/task/?func=detailitem&item_id=119>
Project: Administration
Submitted by: Mathieu Roy
On: lun 02.02.2004 � 02:00
Should Start On: lun 02.02.2004 � 00:00
Should be Finished on: jeu 02.09.2004 � 00:00
Category: Services Functionalities
Priority: 1 - Later
Resolution: None
Assigned to: None
Percent Complete: 0%
Status: Open
Effort: 0.00
Summary: webalizer statistics for download area + homepage per project
Original Submission: We should provide "webalizer statistics for download area +
homepage per project"
Commentaires :
------------------
-------------------------------------------------------
Date: sam 08.05.2004 � 20:00 By: yeupou
No, it is not complex to set up webalizer. However, we need to make apache saving
logs for each area in separate files. That's not a big task either, that's doable. But
it still need to be done.
You are right, what would be need in a minimal script that create a webalizer conf
(hum, it may even not be necessary. Just one conffile + command line args may be
enough).
The robot.txt blocking access to search engines is a good idea, indeed.
However, a script handling webalizer conf creation should not touch cron. There should
be only one cron entry. Otherwise it would not be scalable.
--
How I understand your script, it would be called by the script that create the
homepage area at http://home.gna.org
--
The prefered language is Perl, as all the others scripts are in Perl.
The scripts must be in "use strict;" and should use "use Getopt::Long;" for command
line arguments.
--
The best is to have a script that takes as argument on the command line:
--conffile= path to the configuration file like /var/webalizer/group.conf
--logfile= path the apache log, like /var/log/apache/bygroup/group.log
--outputdir= path to the output directory for webalizer
like /var/www/group/webalizer/
--title= title for the webalizer results
It would be easy then to adapt the script homepage-update.pl to call that script.
No other group info other than the system name is available. The home.gna.org system
in a chroot that have no access to the database or anything else.
--
Another script (a trivial one) like homepage-update.pl should be written to run
webalizer on each conffile, and that script will be run via cron. In fact,
homepage-update.pl would only need very trivial changes for that.
--
So if you can write the first script, it would be easy for us to include it in our
bunch of scripts.
If you want, we can give you write access to the cvs repository, which is not public
(but all the code is GPL).
-------------------------------------------------------
Date: ven 07.05.2004 � 10:36 By: djobet
>From my limited knowledge, setting up webalizer is not too complicated : we need to
>set up a webalizer.conf file, plus set up a cron job to launch webalizer once a day.
I guess we have to provide a tool (in which form ? perl ? bash ? other ?) that creates
the conf file from the project info (in which form can we retrieve the project info ?).
One bothering task with webalizer is to regularly check the logs to add IgnoreReferrer
on xxx site (they use webalizer as a way to increase their google ranking).
I guess we should add a robot.txt file forbidding the search engines to reference the
webalizer page...
If you can tell me what kind of tool I can use and how I can get basic information on
the project (such as the name, the path on the servers, ...) I can create a script
that creates the
- webalizer.conf
- add an entry in the cron
I think we will need to think if we want a referrer entry in the webalizer page (I
think that's a cool feature because I can see who is talking/using of my project) and
in that case how can we fight against porn sites.
See my last webalizer entry : http://www.nosica.net/webalizer/usage_200405.html
CC List
-------
CC Address | Comment
------------------------------------+-----------------------------
nicoo | any roadmap at this point?
For detailed info, follow this link:
<http://gna.org/task/?func=detailitem&item_id=119>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Project mailing list
[EMAIL PROTECTED]
http://mail.gna.org:8080/listinfo/project
