From: malmberg@eisner.decus.org
Sent: Monday, January 29, 2001 7:07 PM
To: Info-VAX@Mvb.Saic.Com
Subject: Re: samba 2.0.6

In article <Oozvf8elmJpy-pn2-l3kuYITIn1NX@Tom2>,
Thomas.Hahnemann@nospam_s-t.de (Thomas Hahnemann) writes:

> Now it runs. My mistake was to specify "interface =" instead of
> "interfaces =" and to look only into  the text files assuming they
> contain then same information like the html docs.

> But the problem with large directory still remains.

My suspicions are that it is a result of internally SMBD effectively
calling stat() several times for the display of each file.

This requires translating the filename from DOS format through a
codepage with a small loop and then scanning it again to translate
any "\" found to be "/"., and then the resulting filename must
be translated to VMS converting any funny characters to either
ODS-2 limitations or ODS-5.

Then there is also a section of code that tries to simulate a
case insensitive filesystem on UNIX.  This part can be disabled
by a setting in smb.conf.  In my tests it seemed to help a
little bit.  There was a report posted recently that made
the client have to use lower case when retrieving files on an
earlier version of SAMBA.  I do not recall seeing that, but again
I was looking at directory listing times and may have missed testing
for that side effect.

Plus it must try to create a unique 8.3 filename.  This is suppose
to be able to be disabled by a smb.conf setting.

Now if you are displaying a directory in a Microsoft Window Explorer
window on the client, it is searching each file of certain types for
an icon to display.

With Oplocks enabled, this could slow things down a bit.

> Now I stop the processes by typing
>   stop "NMBD 2.0.6"
> and
>   stop "SMB_    myhostnnn"
>
> Q: How can I shutdown samba ?

You have got the NMBD shutdown down pat :-)

The "SMB_ *" names will eventually go away after a time when they
discover that the client has not transferred any data.  Since
the SMB or Lanman protocol is mostly "connectionless" if there
are no files actively open, the "SMB_ *" processes can go away
in idle periods even if you have a drive mapped.  The next
activity will cause your TCPIP program to start up a new
"SMB_ myhostnnn" process or processes.

Shutting the SMB programs down is basically issuing the commands
specific to the TCPIP program you have to disable the starting
of the "SMB_ *" processes.

For SAMBA 2.0.6 on OpenVMS, when you have disabled your TCP/IP
program from starting the SMBD process, you can run the SMBD process
interactively and redirect the output to SYS$OUTPUT:.

Due to either a bug or a feature in the UNIX code, the debug level
must be 4 or higher for this redirection to take place.

The fun part in running SMBD interactively in debug is finding the
places where the client will time out, and where it will wait for ever
for the server to respond.  Also occasionally one of the systems on
your network will happen to try to browse your server just as you were
trying to connect up a client, thus hijacking your debugging session.

Have fun,
-John
wb8tyw@qsl.network
Personal Opinion Only.

You may want to consider joining the SAMBA-VMS (at) SAMBA.ORG mailing.
list.  It does have a lot of overlap with the people here, but is
usually not too active.  There may be some people that are on that
list that could be interested in what you are doing.

To sign up to for the SAMBA-VMS mailing list, see your local mirror
of http://www.samba.org