I changed the ExcludePath to:
.*\.sys$
The error still occurs. I do a ticket created for an identical issue.
It looks like there is a patch to fix the problem, but I’m not sure how to apply said patch
Hi there,
On Thu, 4 Mar 2021, Michael Kyriacou via clamav-users wrote:
> Hello, I am running into a bug/error when adding an ExcludePath to my clamd.conf
> I am running Ubuntu 20.04.2, with clamav 0.103.1(from source)
> When I add the line: ExlucudePath .*\.sys$, the following issues occur when
> running the command "clamdscan -m --fdpass /path/to/mounted/filesystem
> *Note: This error occurs only when using the -m parameter in combination
> with --fdpass against a Mounted filesystem other than the main harddrive*
>
> Running it against my home directory
> [image: image.png]
> Running it against a mounted filesystem with data in it
> [image: image.png]
> I tested this on over 50 different mounted filesystem, and the same error
> occurs.
>
> Is there any fix to this?
You are using the asterisk charater in your command lines incorrectly.
You need to quote it (and any other 'special' characters you use in a
command), or (in the case of a path) quote the entire path. Otherwise
the shell will expand the asterisk which will result in a command very
unlike the one you intended. See the 'man' page for the bash shell:
man bash
But, even with incorrect command lines, there should not be segfaults.
Check the ClamAV bugzilla, and if you don't find anything which seems
to describe your issue please either open a new report yourself or reply
here and someone will be able to open one:
https://bugzilla.clamav.net/buglist.cgi?component=clamd&product=ClamAV
--
73,
Ged.
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml