Yavuz Maşlak schrieb: >> Is your proftpd running chrooted? > > Yes I running proftpd as chrooted. when I remove chrooted, proftpd will > run with clamd.
Ok, that explains it. >> In that case you'll have >> to put clamd.sock somewhere inside its chroot jail, and >> strip the chroot path from the "ClamLocalSocket" parameter. > > I have some virtual users. I don't know what that means in this context. Does proftd create a different chroot jail for each virtual user? > Could you give an example how I will have to put clamd.sock and other > needed jobs. ? Example, no. I don't use proftpd myself. Just the theory: If program A runs chrooted at /prog/A/chroot/jail and accesses a file (or socket) at /path/to/file then the access really goes to /prog/A/chroot/jail/path/to/file. So if your proftpd runs chrooted to /chroot/of/proftpd/for/userX and wants to access /var/run/clamav/clamd.sock then that socket must really exist at /chroot/of/proftpd/for/userX/var/run/clamav/clamd.sock and you must tell ClamAV to create its socket there. (You may also get away with leaving it where it is and creating a hard link into the chroot jail; a soft link will definitely not work.) HTH T. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
