--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joel Hammer wrote:
| #!/bin/bash
| case "$1" in
| start)
| killall smbd
| killall nmbd
sleep 5 wouldn't hurt...
| /usr/local/samba/bin/smbd -D
| /usr/local/samba/bin/nmbd -D
| ;;
or even something along the lines of:
killall smbd
killall nmbd
f
ok ages to spot such a simple error
-Original Message-
From: D. Rick Anderson [mailto:[EMAIL PROTECTED]
Sent: 06 June 2003 18:59
To: [EMAIL PROTECTED]
Subject: [Samba] stability
I'm having problems when I restart the smb server with it not coming back
up. As near as I can tel
That's nice. I guess it's a good thing that SigTerm (Sig 15) is the
default signal for killall. (Almost like you would expect, no?)
On 6 Jun 2003, Oscar A. Valdez wrote:
>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
>From the killall man page:
killall sends a signal to all processes running any of the
specified commands. If no signal name is specified,
SIGTERM is sent.
-- Original Message --
From: "Oscar A. Valdez" <[EMAIL PROTECTED]>
Date
- Original Message -
From: "Alex" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 4:03 PM
Subject: Re: [Samba] stability
> I had similar problems about a year ago with 2.2.3a-- the problem was a
> stale PID.
> Long story short,
>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 o
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/loca
killproc is defined in /etc/rc.d/init.d/functions that's called by the rc scripts. In
my case it was only killing one nmbd while multiples were actually running.
-- Original Message --
From: "D. Rick Anderson" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED
killproc doesn't even exist on this machine, yet it was how the script was
'attempting' to stop nmbd. I'm sure that the version (2.2.7a) installed
with RedHat must have been using just kill.
I changed it to killall, but I'm going to wait until all of the users
logoff and go home before I start dor
Are you sure that all of the nmbd processes are actually stopping the first time you
issue the command. I had to change the killproc command to killall on one system so
that nmbd would actually be completely stopped.
Dan
-- Original Message --
From: "D.
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 iss
hi
im would be interestet in your experense with samba in larger enviroments
with more than 200 clients
stability of samba?
stability of the logon and userdatabse?
and the scalability?
thanks hanspeter
--
To unsubscribe from this list go to the following URL and read the
instructions: http
13 matches
Mail list logo
