Captured from #2441575: clanscan return codes no longer provide details of errors

It may also be an idea to provide an option to do something like try the scan again with some extra options (--verbose --debug perhaps?) and log the output of that. Alternatively just being able to pass extra options to the executable all the time would be a useful addition.

Comments

manarth’s picture

Status: Active » Patch (to be ported)

Fixed in D8 release - parameters can be passed to the executable.

We should probably back-port this to D7.

  • mcdruid committed 06dc2f6 on 7.x-1.x
    Issue #2474079 by mcdruid: Provide optional parameters to the executable...
mcdruid’s picture

Status: Patch (to be ported) » Fixed

Added to 7.x-1.x

  • mcdruid committed e38b411 on 7.x-1.x
    Issue #2474079 by mcdruid: delete executable params variable on...
drumm’s picture

Status: Patch (to be ported) » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

chicagomom’s picture

Is there any documentation as to which parameters are usable? I have tried --exclude=[stuff] in the "executable parameters" area of the config page [7.x-1.x] and it does not appear to work.

manarth’s picture

Hi chicagomom,

In theory, it should pass any parameters that are acceptable to the version of ClamAV that you're using. It might be worth checking which parameters are acceptable to your version of ClamAV: the ClamAV documentation should hopefully answer that question.

If you find that you're passing a parameter which should be accepted but isn't, can you let us know more about which parameter it is? It's possible that maybe we're not passing the parameter in the right way, which is something we should be able to fix.