I'm noodling around with Ubuntu 10.4.1, latest updates and kernel (2.6.32.24?).

Anyway, I run ClamAv as root and it goes fine through almost all of my system (huge amount of it), including several virtual devices, where it hangs on pan0, which has some association with my network (eth0 would be for wired connection, and wlan0 for wireless, and pan0 is listed also, but I'm not at that machine right now, so I can't tell why it shows up. wlan0 is what I use to connect to the internet).

Is there an issue for clamAV with virtual devices? Any workaround? I had to terminate the scan after it stayed hung for over 5 minutes on pan0.

Thanks.

I don't know if there's issues with ClamAV and device files as I notified BitDefender of the same about two years ago. Maybe it depends on your engine version because for any /dev/* entry my ClamAV returns "ERROR: Not supported file type".

I downloaded, installed, and ran, ClamAV yesterday (6 Sept.), so I'm thinking it should be the latest engine version available. It ran fine, and even handled several virtual devices, hanging only on pan0.

Is there any particular argument syntax I should pass to ClamAV at the command line when starting it so that it will bypass /dev in its entirety?

Thanks

--exclude=/dev ?

I'll check it out this evening. Thanks.

While I do not know the correct answer to this problem, I have seen hackers create directories in /dev/ to hide back doors running on the server. Though I would say it is very rare and not something a kid using pre-made scripts would know how to do.

Found out that Pan0 is my bluetooth service, and by stopping the service i should eliminate that particular hang. I have found other hangs, in /sys/devices/virtual, so I will probably have to exclude the entire folder.

ClamAV has never given me such trouble before.