I'm running SuSE 9.1 with the latest updates, and Samba is freezing my machine. Here's what shows up in the system log (numerous similar timeout entries omitted): Nov 30 15:00:07 townserver kernel: smbfs: unsupported module, tainting kernel. Nov 30 15:02:09 townserver kernel: smb_add_request: request [c1e66e80, mid=7582] timed out! Nov 30 15:02:40 townserver kernel: SMB connection re-established (-5) Nov 30 15:09:39 townserver kernel: smb_add_request: request [c1e66e80, mid=7597] timed out! and after a reboot: Nov 30 15:19:09 townserver syslogd 1.4.1: restart. A Google search revealed the following information: -- begin quote -- It seems there's a bug in the kernel that everybody knows about, but us. Here's a clip of what I've found via a google dig: "The 2.6.x sendfile() system call seems to be broken in the kernel. Try adding "use sendfile = no" to your smb.conf." Added that single configuration line and everything is now operating as expected. Even though the default setting for "use sendfile" is no, it is either not being recognized during samba startup or is being toggled "yes" by some other config statement. Either way, this'll do it. While I was in the smb.conf I added: use sendfile = no large readwrite = no max xmit = 16644 We're back to normal and maybe even a bit better. I can go home now. -- end quote -- However, adding the suggested sendfile and other entries did not solve the problem, though it revealed a Samba bug in the processing of sendfile by SWAT: no matter how you change the "use sendfile" entry, the change is not reflected in the smb.conf file. Anyone else seen this, or have a clue about what is ailing smbfs? Paul