hank_chu
2004-Apr-15 13:17 UTC
[Samba] How to reduce the memory used by Samba and its connection ?
Dear Sir : About the Samba, could you do us a favor to advise us if any comment about the following problem. We used Samba v2.0.7. We are porting the Samba into Linux box. The Linux box is an embedded system with 32MB memory only. Because Samba takes around 1.5MB memory for each connections, it takes lot sof memory for multiple connections. It exhausted the memory of box. In order to increase the NO# of connections of Samba in this Linux box, we try to reduce the memory size of Samba. But it is really a big efforts. Could you do us a favor to advise us if any comment to reduce the memory size for Samaba connections ? Thank you. Best Regards. Netronix Inc. Hank ChuFrom pupilla at hotmail.com Thu Apr 15 13:19:23 2004 From: pupilla at hotmail.com (Marco Berizzi) Date: Thu Apr 15 13:20:19 2004 Subject: [Samba] Fw: md5 fail on large file Message-ID: <Sea2-DAV63HZOzTBoLI000250bc@hotmail.com> Me again. I have upgraded to linux kernel 2.6.5. However this problem hasn't gone away. The md5 check is fine, coping the same file from NT4TSE to a Windoze 2000sp4. Coping the same file from a windoze 2000sp4 to the samba share is ok. So the problem is between NT4TSE and samba. NT4TSE --> SAMBA = KO WIN2k --> SAMBA = OK NT4TSE --> WIN2K = OK Can anybody help me? Marco Berizzi wrote:> Hello everybody. > > I'm experimenting this problem with > samba 3.0.2a and linux 2.4.25 with > ReiserFS. > When I copy (put) a large file (5GB) > from a Windows NT terminal server sp6a > to the samba-linux box, the md5sum is > different between the two file. Files > size are identical. > I'm using this command to copy these > files from windows to samba: > > xcopy f:\ \\mimas\backup\exchange /e /c /h /r > > I have also tried to delete the old > files from the samba share, but nothing > change: I always get two different md5sum. > With smaller files (400MB) md5sum is > identical. > When I transfer this large file with ftp > (proftpd 1.2.9 on Linux), md5sum is ok. > > These two systems are connected to a 3COM > 100bit/s switch. No collision/no error are > detected at linux side box. Samba doesn't > log anything relevant. No kernel error. > Nothing. Samba box is running Slackware 9.1 > + kernel 2.4.25 + samba 3.0.2a compiled > from sources. > > Hints? > > PS: Please CC me I'm not subscribed to this list.