Closed jksinton closed 7 years ago
Instead of removing the log file for freshclam, could you check whether it's running as a daemon?
If it is, you don't really need to update the database, as it's already updating the database based on the config settings.
If it's not running as a daemon, then you should be able to run freshclam without the lock error.
You can check if the file is in use by the daemon. And you would be right, you shouldn't need to update the DB in such case.
Instead of removing the log file for freshclam, could you check whether it's running as a daemon?
If it is, you don't really need to update the database, as it's already updating the database based on the config settings.
If it's not running as a daemon, then you should be able to run freshclam without the lock error.