samba - Feb 1998 - Browsing/Subnets/ Workgroups >>

> 
> Interestingly, when inspecting the log files, samba appears to be 
> doing the right thing, and the var/locks/browse.dat file on all of the
> master browsers lists all of the domains/workgroups
Further to last posting.

1. If you move a samba server on another subnet OUT of a 
   cross network domain into its own domain, it is NOT deleted
   from browse.dat in the old domain.  A restart on the samba
   server with   WINS support seemed to clear that up.

2. I changed the WORKGROUP on my win95 PC to be the same as the
    samba servers, on my subnet with includes the WINS server, and voila
    all of the workgroups appeared, including the workgroups  from the
    other subnets.  It appears that the local browse masters on the
    other subnets which are pointed to my WINS server are doing the
right
    thing.
    
3.  The trouble is - the samba server (on another subnet) I moved to 
    another domain - still appears in the old domain. It also appears
    in the new domain.

4.  If I did a "tail -f /usr/samba/var/log.nmb" on the 
      WINS server/domain master browser ,
    and then did a view/refreshin explorer,  would I not see a query 
    logged in the log file, as it tries to find the master browser 
    for the domain ???  Currently I do not, even after re-booting the
    PC.  It is almost like it is getting the browse list from somewhere
    else....

Sorry for the length of this, and I hope it is not too confusing,
 but I am really puzzled.  TIA

> Date: Wed, 11 Feb 1998 09:55:37 -0700 (MST)
> From: Kitty Ferguson <ferguson@jabba.hao.ucar.edu>
> To: samba@anu.edu.au
> Is there a way to stop and restart the Samba server without rebooting 
the 
> machine? 
> --Kitty Ferguson		System Administrator - CSMT
> ferguson@hao.ucar.edu		NCAR - High Altitude Observatory	
> tel: (303)497-1556		P.O. Box 3000
> fax: (303)497-1589		Boulder, CO 80307-3000

Of course there is a way to start/stop Samba without rebooting.

This is describe somewhre in the doc of Samba.

The best way for a SysV is this:

Make a symbolic link in /etc/rc3.d to /etc/init.d from the file 
S99samab.server to the file samba.server:
lrwxrwxrwx 1 root  other   24 Jun 27  1997 /etc/rc3.d/S99samba.server -> 
/etc/init.d/samba.server*

Here is the content of the file (taken from the Samba doc)
(replace the /opt/samba/bin path by yours)
terre{root}: cat /etc/init.d/samba.server
#!/bin/sh
#ident  "@(#)samba.server 1.0   96/06/19 TK"    /* SVr4.0 1.1.13.1*/
#
# Please send info on modifications to knuutila@cs.utu.fi
#
# This file should have uid root, gid sys and chmod 744
#
if [ ! -d /usr/bin ]
then                    # /usr not mounted
        exit
fi

killproc() {            # kill the named process(es)
        pid=`/usr/bin/ps -e |
             /usr/bin/grep -w $1 |
             /usr/bin/sed -e 's/^  *//' -e 's/ .*//'`
        [ "$pid" != "" ] && kill $pid
}

# Start/stop processes required for samba server

case "$1" in

'start')
   echo "Starting SAMBA Services: "
      /opt/samba/bin/smbd -D
   echo "   smbd Started"
      /opt/samba/bin/nmbd -D
   echo "   nmbd Started"          
   ;;
'stop')
   echo "Stoping SAMBA Services: "
      killproc nmbd
   echo "   nmbd Stopped"
      killproc smbd
   echo "   smbd Stopped"
   ;;
*)
   echo "Usage: /etc/init.d/`basename $0` { start | stop }"
   ;;
esac


This will accomplish 2 things:
1) start automatically samba at boot.
2) allow tou to start/stop samba at will with these commands:
   /etc/init.d/samba.server stop
   /etc/init.d/samba.server start

Another note:
Most of the parameters of the smb.conf file I read on the fly and you 
don't have to restart Samba.

Hope this help.

-- 
===================================================Gaetan Boudreau, ing/P.Eng.
Administrateur de reseau/Network Administrator
IRCM (Institut de recherches cliniques de Montreal/
      Clinical Research Institute of Montreal)

tel: 514-987-5563   fax: 514-987-5644
Internet E-Mail: Gaetan_Boudreau@IRCM.UMontreal.CA
Internet Web Site: http://www.ircm.umontreal.ca

Hi Jeremy: Does this mean that the right way to handle 100B-T networks
is to take out the TCP_NODELAY socket option? I'm curious why the
performance went down with the switch though. 

I'll try out the patched version you suggest at some point.

Sundar Narasimhan wrote:
> 
> Question re: 1.9.16-patched performance. Hi, I have samba (version
> indicated) running on Solaris 2.5.1. Recently we upgraded from 10B-T
> to 100B-T and now, I periodically notice that performance between
> samba and our NT SP3 clients slows down dramatically. Using snoop -- I
> see that NT writes large packets as before, but samba only sends
> packets that around 300-360 bytes. Needless to say this seems to be
> intermittent and quite frustrating.
> 
Do you have TCP_NODELAY set as a socket option in your smb.conf ?

If so, this could cause the problem as every write from
Samba will then generate a packet.

Upgrading to 1.9.18p2 with oplock support will also
help greatly.

Regards,

Hello,
	I have been running samba as file/print servers for quite some time now
without a hitch. I've recently upgraded 3 out of 4 servers to 1.9.18p2 and
I seem to be having a problem with the new oplocks (or maybe I'm not
understanding exactly how they're supposed to work).
       Here's my scenario.  I work for an electronic publisher.  Writers
write stories and then save them to a samba shared drive so that the files
can be edited/ prepared for delivery.  After the document has been
edited/etc the file is saved onto another samba share where I grab the
files and send them to where they are supposed to go. 
       My Problem...  When the files are saved to my samba share I can not
acces the files because they show that they are still locked.  If I wait
the locks will eventually disappear, but with the writers having deadlines
for delivery it makes it important for me to access the files as soon as
they are available.  Turning off the oplocks makes it possible to access
the files immediately.
	My Question...  Is this normal behavior for oplocks?  I was under the
impression that when the file was closed, or the application terminated the
file's lock should die as well.
							-= Jesse =-

I'd also like to thank the Samba Team for all their hard work.  Since
I've
started using Samba I have been able to get rid of all of our Novell servers,
(except one, but it's next on the list to go) and when I'm through
configuring 
my newest Samba server I'm going to start killing of the NT servers as well.
Thanks guys.