-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maintenance.sh invalid directory, no docs #1
Comments
Hi, this script can be used to cleanup the database regulary. It is just a sample script that you can use to setup a cronjob. The path is just a sample and has to be customized by the user. So I would recommend to change "/var/www/phplogcon/cron/" to the path where you install Loganalyzer. |
Can you clarify what you mean by database? Is this for cleaning the source database (e.g. where rsyslog stores logs) or does LogAnalyzer want to create its own database with a copy/cache of the data, indexes or reports? On many systems, /var/www/* files are readable by the httpd user (e.g. user www-data on Debian) but they are not writeable. So if LogAnalyzer wants to keep any cache data that it maintains itself, we need to create a directory that it can happily write to. The INSTALL file only says that the config.php has to be writeable and only during the setup. In the Debian package, we actually install the static content (PHP files, etc) to /usr/share/loganalyzer so I could modify the cron to refer to that location. If any writeable directory is needed, we would probably need to create it using one of the following: /var/lib/loganalyzer and then make it possible to specify the location in config.php |
It is for clearing the source database, where Loganalyzer reads it's events from. You will find some documentation about the maintenance script here: http://wiki.rsyslog.com/index.php/PhpLogCon_Delete_Records And yes I would recommend to change the path in the sample script to "/usr/share/loganalyzer" then. There is no need for writeable directories unless you create reports and you want to save them rather then view them. |
I notice the package includes a script src/cron/maintenance.sh
This refers to a directory /var/www/phplogcon/cron/ that is not explained in the INSTALL file
Does this script need to be used at all?
Does the admin need to create this directory or install some third party component there?
The reason I ask is because we are making an official Debian package. The package scripts will make all the required directories and set up the cron jobs automatically for the user.
The text was updated successfully, but these errors were encountered: