ClamAv MaxDirectoryRecursion

A very strange coincidence because I have exactly the same issue and planning to post to the forum today with a request to remove the line MaxDirectoryRecursion 15 from the current Openmediavault generated clamd.conf file.

This particular config line is not not needed because Clamav defaults to a value of 15 when this line is not present. I have actually checked that this is accurate on my raspberry pi NAS setup.

The current clamd.conf file is as follows :-

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
{snip}
MaxDirectoryRecursion 15
{snip}

Hence the warning that states that this is file is not user configurable by for example editing the file using Nano because it would be over written every time the plugin gets updated.

It is currently possible to modify the configuration using the extras section of the configuration web page to add a larger value by typing into the extras box MaxDirectoryRecursion 40 which when saved modifies the clamd.conf file to :-

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
{snip}
MaxDirectoryRecursion 15
{snip}
# Extra options
MaxDirectoryRecursion 40

Although Clamav will run with this config file, it still uses the first value of 15 and does not pickup the later value of 40.

If I manually using Nano comment out MaxDirectoryRecursion 15 using #, Clamav then does pickup and use the value of 40 as added using the extras section of the web page.

# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
{snip}
# MaxDirectoryRecursion 15
{snip}
# Extra options
MaxDirectoryRecursion 40

Hence the requested fix, to modify the Openmediavault script so that the line MaxDirectoryRecursion 15 is not added to clamd.conf.

Note that there are also other options to correct this issue but all would involve an update to the plugin.

Zitat von votdev

Please use environment variables to customize OMV settings. See https://openmediavault.readthe…n/5.x/various/advset.html and https://github.com/openmediava…c-clamav-clamd_conf.j2#L5

Thanks, finally my periodic scans can run without errors