samba - Jan 2000 - findsmb patch

Hello Herb, all.  I recently played a bit harder with Samba, as I'm
working on getting it set up for my sister (remotely). I came across
Herb's old 'findsmb' perl script which got me a lot further along
than
I had been.  I wanted to note a small patch I made in order for the
script to deal with 'bad' characters in the machine names:

--- /usr/bin/findsmb    Mon Oct 12 20:03:10 1998
+++ findsmb     Sun Jan 16 10:30:11 2000
@@ -79,7 +79,8 @@

 # do an smbclient command on the netbios name.

-    open(SMB,"$SAMBABIN/smbclient -N -L $name -I $ip -U% |") ||
+    ($ename = $name) =~ s/"/\\"/g;
+    open(SMB,"$SAMBABIN/smbclient -N -L \"$ename\" -I $ip -U%
|") ||
        die("Can't do smbclient command.\n");
     @smb = <SMB>;
     close SMB;


==> end diff

The patch just changes findsmb so that it changes any double-quote
marks in the name into escaped double-quote marks, then protects the
name from the shell with double-quote marks.  Otherwise, machines like
"Lauren's box" gave errors.  There may be a better way to do it,
but
this fixed the error I saw, so :)

-jeff
-- 
According to a recent Justice Department report, the number of jailed
Americans more than doubled over the past 12 years. What do you think
about America's soaring prison population? "I have only one question:
How
will this affect the Internet?"  Dennis Herndon, Magazine Editor
http://www.theonion.com/onion3511/wdyt_3511.html

I am a new Linux/Unix user - had Linux installed by a consultant. 
Everything ran nicely for two weeks or so then Samba started acting 
strangely.

RH 6.0 Linux Server / NT 4.0 SP5 clients - suddenly I am seeing a 
user Samba processes taking 95% -98% of CPU - basically bringing the 
server to its knees (users cannot authenticate and shares are not 
available). The user is not even logged onto the system. I can kill 
the process and generally everything goes back to normal - but about 
50% of the time Samba at root will shoot up to 95% CPU. I try to kill 
samba at root with KILL PID but am not able to kill the process. 
Requires a restart to clear up the mess. Has happened once a day over 
the last week. This can happen when I have only two NT users logged 
onto the system (typically I have 30-40 users during work hours).

If anyone can offer some suggestions on how to troubleshoot this 
problem and suggest solutions.. I would appreciate it.

Best regards,
Hugh Evans



*************************************************
This Email is "Confidential" - the content of this Email and any 
attachments, if any - shall not be distributed beyond the intended 
recipient(s) without the specific authorization from the originator 
of this Email"