AW: Samba Solution ? [was] Beware: Samba is a hoax

[Rudolf Kollien]

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 at 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 at avantel.com [mailto:alex at 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
>
>
>