W3Perl administration
(Version 2.91)
Your first step will be to create a configuration file. You can have several configuration files for one server or one configuration file for each of your server. This file have everything to customize your stats.
| Config files |
|
|
|
|
You could use as many configuration files as you need if you want to view different stats with the same logfile.
|
Use this section if you just need to change some values in your configuration files or want to use default ones. This part will load your current data and will allow you to change the values.
|
|
|
|
|
If you need to get several configuration files but nearly similar, use this to load an existing configuration file, modify it and save it with another name. |
If you want to delete some of your configuration files, this is the right place.
|
| Launch |
|
|
|
|
If you don't have a telnet access or you are not allowed to have a crontab, you can launch the scripts via a HTML page. For each scripts, options are available. |
You can choose which scripts you want to run and when you want to run each of these scripts. |
| Misc |
|
|
|
|
If you are using several configuration files, you may be interested in a short description about your stats. They are sorted by accesses. |
Make sure your configuration files are valid.
|
| Upgrade/Install |
|
|
|
|
If you want to upgrade to the latest release, please use this script which will detect any change in the configuration file. It works from version 2.69 |
If you have installed the package from a ftp client (without telnet) or you have upgraded w3perl from a previous version, you should run this script first to enable your cgi to run. It will fix path inside the scripts according to your setup. |
