I think it's important for the samba developers/programmers/hackers to see the samba log created while accessing this file. Be so kind and clear your samba log file, insert a "debuglevel=12" in the smb.conf, restart the syslogd with a kill -1, create the file which caused the problem, start you win client and access the file. Save the log, switch your debuglevel back to 1 or 2, restart syslogd and send the file to the group. System-Consulting Kollien Rudolf Kollien Email: kollien@kollien.de Our home on the net: http://www.kollien.de *************************************************************************** Never trust a operating system you have no sources for *************************************************************************** Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. *************************************************************************** This line is for the US NSA only: sex bomp terror attack drugs shit fbi cia> -----Urspr?ngliche Nachricht----- > Von: alex@avantel.com [mailto:alex@avantel.com] > Gesendet am: Samstag, 6. Februar 1999 18:18 > An: Multiple recipients of list > Betreff: Samba Solution ? [was] Beware: Samba is a hoax > > Let me start by thanking the many people who replied to my cry > for help. I > received far fewer flames than expected and the majority of replies were > helpful and supportive. > > I (think?) the problem is fixed but I do not understand what was broke. > Here's what I found and what I did (I'm hoping someone > understands why this > worked) > > Since the listing of shared files on the Samba host (either in a > dos box or > with explorer) was causing my W95 client to freeze I decided to see if a > particular file was causing the problem. After a 'net use x: > \\sambahost\tmp' > I switched to x: and instead of asking for 'dir' I used 'dir *.log' - NO > FREEZE! And I got a listing of the 4 log files in the \tmp directory > > I kept this up until I found one single file that would cause my system to > freeze (repeatable). So I removed that file from the \tmp directory and > tried again. This time, no freeze. Everything worked as it was > supposed to. > > So my question - is there any reason that a particular file should cause a > failure such as the one I experienced. Here's the filename listing - > there's nothing unusual about the file and it causes my system to freeze > regardless of what's in the file (I deleted it initially and > recreated it - > same size, content unknown). If I re-insert this file into the \tmp > directory I get my freezes back. > > -rw-r--r-- 1 root alex 31 Feb 6 10:51 000b208e.lpq > > (I changed it from the original lpq.000b208e to see if that made any > difference but it did not.) > > Is this just a fluke or is there a reason that this could be the cause? > > I'm baffled. > > Alex > > >
I did what several people on this list suggested and sent some info to the samba bugs list. I got a reply from John H Terpstra - Samba-Team, who said: 'I did not find anything unusual about the info you sent.' He asked for and got some additional log and tcpdump info too. However, I am starting to suspect a name mangling configuration problem that confuses W95 (or samba?). Here's why : I created two empty directories on the Samba server. I could access these from explorer without W95 crashing. Then I copied files into those directories from the windoze box using explorer. As long as the file was in 8.3 format - no problem. I could put in as many as I wanted - no delays & I could list them. Then I copied in two W95 long filename files. The first went fine, it was called 'novell_products.html' The second caused trouble, it was called 'telecom.y2k.html' A check of the Linux box showed that the file had copied in OK, but I could no longer list the files in that directory (browse the share as MS would say ;p ) I went for lunch to see if W95 could recover but no such luck - reboot time. It is very possible that I have the mangling options set wrong (all on default) so I'm going to see what I can do there. (sent to bugs list too) If anyone has a combination of mangling settings for Samba that is supposed to work for W95 long filenames that would be very much appreciated. I'm trying some combination now but I find it difficult to understand the implications of all the possible settings especially in various combinations. TIA for any suggestions Alex At 04:06 PM 2/6/1999 -0500, Rudolf Kollien wrote:>I think it's important for the samba developers/programmers/hackers to see >the samba log created while accessing this file. Be so kind and clear your >samba log file, insert a "debuglevel=12" in the smb.conf, restart the >syslogd with a kill -1, create the file which caused the problem, start you >win client and access the file. Save the log, switch your debuglevel back to >1 or 2, restart syslogd and send the file to the group. > > >System-Consulting Kollien >Rudolf Kollien > >Email: kollien@kollien.de >Our home on the net: http://www.kollien.de >*************************************************************************** >Never trust a operating system you have no sources for >*************************************************************************** >Buying an operating system without source is like buying >a self-assembly Space Shuttle with no instructions.