[Samba] vfs_scannedonly fails to connect to socket.
Hello All, I'm trying to configure the scannedonly module with ClamAV on OpenSuSE 11.3 but it's failing to connect to the clamav socket and I can't figure out why. Clamd is running and the socket is has 666 permissions. I've increase log level = 5, tried stracing the processes but nothing. Any thoughts on what to try next? OpenSuSE 11.3 samba-3.5.4 clamav-0.97 [share] path = /srv/samba/share read only = No browseable = No directory mask = 0775 create mask = 0644 oplocks = False # Virus scanning vfs objects = scannedonly scannedonly:domain_socket = True scannedonly:socketname = /var/lib/clamav/clamd-socket scannedonly:hide_nonscanned_files = True ls -l /var/lib/clamav/clamd-socket srw-rw-rw- 1 vscan vscan 0 May 19 12:29 /var/lib/clamav/clamd-socket [2011/05/19 12:46:32.541300, 2] modules/vfs_scannedonly.c:207(connect_to_scanner) failed to connect to socket /var/lib/clamav/clamd-socket Initialising custom vfs hooks from [scannedonly] vfs module [scannedonly] not loaded - trying to load... Module '/usr/lib64/samba/vfs/scannedonly.so' loaded Successfully added vfs backend 'scannedonly' Successfully loaded vfs module [scannedonly] with the new modules system [2011/05/19 12:46:32.822708, 2] modules/vfs_scannedonly.c:207(connect_to_scanner) failed to connect to socket /var/lib/clamav/clamd-socket [2011/05/19 12:46:33.980909, 3] modules/vfs_scannedonly.c:264(flush_sendbuffer) scannedonly flush_sendbuffer: error sending on socket 34 to scanner: Transport endpoint is not connected (107) [2011/05/19 12:46:33.980953, 2] modules/vfs_scannedonly.c:207(connect_to_scanner) failed to connect to socket /var/lib/clamav/clamd-socket [2011/05/19 12:46:33.980965, 2] modules/vfs_scannedonly.c:302(flush_sendbuffer) scannedonly flush_sendbuffer: failed to send files to AV scanner, discarding files.smbd_dirptr_get_entry mask=[*] found dperusich/test.txt is being scanned for viruses fname=test.txt is being scanned for viruses (test.txt is being scanned for viruses) smbd_dirptr_get_entry mask=[*] found dperusich/eicar.com is being scanned for viruses fname=eicar.com is being scanned for viruses (eicar.com is being scanned for viruses) [2011/05/19 12:46:33.993187, 3] modules/vfs_scannedonly.c:264(flush_sendbuffer) scannedonly flush_sendbuffer: error sending on socket 37 to scanner: Transport endpoint is not connected (107) [2011/05/19 12:46:33.993216, 2] modules/vfs_scannedonly.c:207(connect_to_scanner) failed to connect to socket /var/lib/clamav/clamd-socket [2011/05/19 12:46:33.993228, 2] modules/vfs_scannedonly.c:302(flush_sendbuffer) scannedonly flush_sendbuffer: failed to send files to AV scanner, discarding files.Transaction 173 of length 188 (0 toread) -- Later, Darin -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] print driver options different on samba
Jason Balicki wrote: What subsystem and on what OS are you running Samba? I'd bet that it's not an issue with Samba, per se, but an issue with the underlying printing system. If you're using CUPS, check to see if CUPS sees all the options. ok, redhat 7.3, samba 2.2.7, and i've switched from lprng to CUPS 1.1.14. both samba and cups are the latest updated version from redhat. Also, if you are using CUPS, you can probably just use the PPD that's on the Windows machines. i used the PPD from the windows machine to configure the CUPS printer. this worked fine, CUPS see's all the configurable options, all 13 different paper sizes. but still when i configure on the win2k client i only get 5 paper sizes. One more if: If you find that your underlying printing system (be it CUPS or whatever) does not see all the options, you need to fix that first, before you can ask for more help here. Contact your friendly neighborhood print system mailing list. i can make avialable the PPD and .inf if necessary. -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] print driver options different on samba
hello, i have a toshiba FC22 printer/copier which is attached to a fiery Z4 RIP and i'm running into a driver option issue. the print driver is a slightly modified version of the adobe postscript driver 5.2, more trays, paper sizes, etc. when i setup this printer via either a local win2k TCP/IP printer or network printer on a win2k or nt4 server i get all the paper sizes, trays, etc. yet when i set it up on the samba server i'm only getting like 5 of the paper options, compared to 13 on the win2k server. any thoughts as to why this is happening? -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] print driver options different on samba
What subsystem and on what OS are you running Samba? I'd bet that it's not an issue with Samba, per se, but an issue with the underlying printing system. If you're using CUPS, check to see if CUPS sees all the options. i'm running redhat 7.3 with LPRng-3.8.9 that's included with the distribution. i'm using the generic postscript driver as there is nothing specificly for the fiery z4. Also, if you are using CUPS, you can probably just use the PPD that's on the Windows machines. If you're not using CUPS, you should be using CUPS. :) i'll give cups a try. this is just a test system so switching from lprng isn't a problem. thanks -- Darin Perusich Unix Systems Administrator Cognigen Corp. [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
