Hi there,
On Mon, 11 Nov 2019, Michael Newman via clamav-users wrote:
>> On Nov 11, 2019, at 00:00,G.W. Haywood wrote:
>>
>> Exactly what do you do in order to obtain
>> this message? Does it appear in a terminal session, in a log file,…?
>
> I run clamscan from a bash script with this command:
>
> /opt/local/bin/clamscan -r --quiet -i -l $log $scandir --exclude-dir="$exclude" --exclude-dir="$exclude2" --stdout >>$log 2>&1
That leaves quite a lot to the imagination. :/ Ideally we'd want to
know the values of all the variables in the command. It doesn't much
matter about $log, but $scandir and the two '$exclude's are important.
> I have no idea if the MacPorts reclaim removed all of clamav.
I think you might need to look into that, I'm sure there must be
adequate documentation. But to avoid any geese-chasing it would be
better not to jump to any conclusions about broken installations at
this stage. It might not be broken, it might just be scanning in a
different way from how it used to be, or something in the filesystem
might have changed. The error message seems to be telling us that
you're scanning a disc partition rather than a file, and I wonder if
for example one of the '$exclude's is not being set correctly - this
might for example result in asking to scan something like partitions
in '/dev' when you don't intend to. If they're scanning filesystems,
most people will just scan the files, not the partitions. You may
have particular requirements, but if you do I'd have expected that you
would have mentioned that by now.
> Is there something I can do to have clamscan give me more
> information about the sector size problem?
The 'man' pages for the various ClamAV tools are a very good resource.
If you remove the '-i' it may let you see what's being scanned at the
time of the error. If it's as simple as something that shouldn't be
scanned then maybe you'll see that and that might lead to something
like a failure to set an $exclude in the script or whatever calls it.
If that doesn't help you might replace '--quiet' with '--debug' and
run the command, but I don't know how much help that will be. And be
aware that making deductions from what you see in the log files isn't
always straightforward.
I have to say I'm no fan of scanning Unix-type filesystems like this.
--
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