[Samba] stability

[Oscar A. Valdez]

>From the smbd man page:

"To shut down a user's smbd process it is recommended that SIGKILL (-9)
NOT  be used, except as a last resort, as this may leave the shared
memory area in an inconsistent state. The safe way to terminate an smbd
is to send it a SIGTERM (-15) signal and wait for it to die on its own."

and from the nmbd man page:

"To shut down an nmbd process it is recommended that SIGKILL (-9) NOT be
used, except as a last resort, as this may leave the name database in an
inconsistent state. The correct way to terminate nmbd is to send it a
SIGTERM (-15) signal and wait for it to die on its own."

Oscar

El vie, 06-06-2003 a las 14:06, Joel Hammer escribió:
> I think you might be helped by looking at the startup scripts and see just
> what is hapening.  You don't need fancy scripts to start and stop samba.
> For example, here is all I have in mind:
> 
> #!/bin/bash
> case "$1" in
>  start)        
>   killall smbd
>   killall nmbd
> /usr/local/samba/bin/smbd -D
> /usr/local/samba/bin/nmbd -D
>   ;;
> 
>  stop)
>   killall smbd
>   killall nmbd
>  ;;
>  reload)
>  kill -SIGHUP `cat /usr/local/samba/var/locks/smbd.pid`
>  kill -SIGHUP `cat /usr/local/samba/var/locks/nmbd.pid`
>  ;;
>  *)
>  echo Usage: 
>  echo start stop reload
>  ;;
> esac
> exit 0
> 
> To find where your binaries are, just run:
> which smbd
> which nmbd
> 
> To find where your logs and such are, this MIGHT help:
> strings `which smbd` | grep samba
> 
> You can modify this to take into account your own configuration.
> You can also run nmbd from the command line and increase debugging to see
> what is happening in case nmbd is crashing. You can also look in your nmbd
> log.
> 
> Joel
> 
> 
> On Fri, Jun 06, 2003 at 10:58:33AM -0700, D. Rick Anderson wrote:
> > I'm having problems when I restart the smb server with it not coming back
> > up. As near as I can tell it's actually NMBD that's having the issue. I'm
> > running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just
> > upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a
> > 
> > When I issue:
> > #service smb restart
> > 
> > It says that it shut down and restarted ok, but then nobody can logon to
> > the domain, so I issue it again and it tells me that it couldn't kill
> > nmbd, but then it starts it OK, and I can get everyone on.
> > 
> > There's also been a few times where it just stopped accepting logons,
> > after accepting them for most of the day, so I restart it, and it tells me
> > then that it couldn't kill nmbd either.
> > 
> > testparm doesn't find anything wrong with my config. Does anybody know of
> > a way to stabalize this?
> > 
> > Thanks,
> > 
> > Rick
> > 
> > 
> > 
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> > I'm having problems when I restart the smb server with it not coming back
> > up. As near as I can tell it's actually NMBD that's having the issue. I'm
> > running RedHat 9.0 on a Compaq ML-370 with Dual 1.2GHz P3s and I just
> > upgraded Samba to 2.2.8a-1 after having this same problem with 2.2.7a
> > 
> > When I issue:
> > #service smb restart
> > 
> > It says that it shut down and restarted ok, but then nobody can logon to
> > the domain, so I issue it again and it tells me that it couldn't kill
> > nmbd, but then it starts it OK, and I can get everyone on.
> > 
> > There's also been a few times where it just stopped accepting logons,
> > after accepting them for most of the day, so I restart it, and it tells me
> > then that it couldn't kill nmbd either.
> > 
> > testparm doesn't find anything wrong with my config. Does anybody know of
> > a way to stabalize this?
> > 
> > Thanks,
> > 
> > Rick
> > 
> > 
> > 
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
Oscar A. Valdez
Plastipak, S.A. de C.V.