As Chapter 52 explains, you can create a Webmin user or group that has access to only a limited subset of the features of most modules. In the case of the Webalizer module, you can grant a user the rights to edit options for and generate reports from only some of the logs on your system. This can be useful if your system hosts multiple Apache virtual servers, each owned by a different person. As long as each server has its own separate log file, you can give a Webmin user the rights to manage both a virtual server and its log report.
Once a user has been given access to the module, you can use the following steps to limit him to only some of the log files on your system:
Once a user has been restricted in this way, he will be able to use the module to set up reporting for only those log files in the directory set in Step 6. Reports will only be generated as the UNIX user specified in Step 5, which stops the Webmin user from overwriting files that he would not normally be able to at a shell prompt. This makes the module quite safe for untrusted people to use, although a malicious user could set up a reporting Cron job that runs extremely frequently and uses up an excessive amount of CPU time.
You can set the paths that the module uses for the Webalizer program and its global configuration file by using the module configuration form, reachable through the standard Module Config link on the main page. When clicked on, it displays a form containing the fields shown in Table 39.1.
3.145.204.201