I have the scanner installed on on of my VM's, Red Hat Enterprise Linux Server release 6.10, and this is what I am getting:
[root@vantage scanner]# uvscan --summary --verbose /
McAfee VirusScan Command Line for Linux64 Version: 126.96.36.199
Copyright (C) 2016 McAfee, Inc.
(408) 988-3832 LICENSED COPY - August 17 2018
AV Engine version: 5900.7806 for Linux64.
Dat set version: 8987 created Aug 16 2018
Scanning for 668707 viruses, trojans and variants.
/dev/sdb ... is not supported.
/.autofsck ... is OK.
Summary Report on /
Total files:................... 1
Not Scanned:................... 0
Possibly Infected:............. 0
@JamesKrych It looks like you're not actually invoking a scan, but rather doing a compatibility check to confirm 15 locations are able to be scanned. When trying to invoke the scan, it looks like you need the --load switch preceeding your directory if the intent is to scan immediately. Please see the examples on page 19 of the CMD for UNIX Product Guide, PD26748.
Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please give kudos or select "Accept as Solution" in my reply, as appropriate, so together we can help other members?
I am trying and the example you mentioned has the use of a config file to specify what parameters are being used.
My problem is that I kep on getting /dev/sdb ... is not supported.
And, the scan terminates.
-- load is, as far as I can see, to load a particular scanning configuration. The screenshot looks sane, 15 files total,15 files clean. Where is the problem? Put an Eicar.txt inside the folder and see if its picked up or download a ready made one from here: http://www.eicar.org/85-0-Download.html.
I will try that file you mentioned.
I am finally seeing some results that make sense. What was throwing me off was the /dev/sdb ... is not supported.
Ah I see, /proc as well as /dev are locations that do not host "files", that can lead to all sorts of weird things I suppose. Looking at your first post, I can see the "/" now, bad idea :-).
Better specify directories to be scanned, like /usr explicitly, not sure why it moaned about /dev/sdb when /usr/local/uvscan had been specified as scan location (I'm by no means a ~nix expert)