The document is now out-of-date as the 'oav' USE flag was dropped a while back. If someone uses the example provided Samba will have some issues. See http://forums.gentoo.org/viewtopic-p-5078265.html. Reproducible: Always Steps to Reproduce: 1. Use the sample configuration from the doc Actual Results: Samba should work Expected Results: Samba doesn't, complains Commenting: vscan-clamav:config-file = /etc/samba/vscan-clamav.conf vfs objects = vscan-clamav from smb.conf fixes the problem.
Sorry about the incomplete bug. Samba returns: NT_STATUS_BAD_NETWORK_NAME. I just reproduced it on my install. Samba version: [I--] [ ] net-fs/samba-3.0.28 (0) Also, commenting out: vfs objects = vscan-clamav by itself fixed the problem.
I guess we may have to take out references to ClamAV altogether, as the inline support for it within samba was removed: (http://forums.gentoo.org/viewtopic-p-5078265.html?sid=d0fd2c77140733aa55e3d3fabf15d7e6#5078265) CCing the Samba and ClamAV maintainers for comment.
I removed the 'oav' USE-flag since the samba-vscan plugin patch isn't maintained anymore. I'm sorry, but I have no alternative atm.
Alright, I dropped everything from the guide that referred to virus scanning, ClamAV, oav USE flags, scanning Windows shares, and the like. Our guide now only talks about Samba and CUPS. It's drastic, but it seems it's the only choice.
