Parent daemons don't kill children when terminated?
davec-b at rogers.com
Tue Jul 11 16:33:05 GMT 2006
I remember a discussion of this, which I'd characterize as
a resiliency change.
If the parent smbd is killed or dis
unintentionally, the child smbds continue to provide service
to their users.
A new parent smbd can be launched, and will pick up all
new requests for connections.
From the Solaris point of view, the service and fault managers
need to keep an nmbd and a parent smbd running, so that if
a child smbd dies, the client can reconnect.
If the entire machine, domain or zone dies, then an external
mechanism needs to start a new one, possibly on new hardware
because the old one has caught fire (;-))
Active-active and high-performance clusters will probably
need some kind of close relationship with Samba, which is
quite a different subject, mostly having to do with tdb
locking-performance discussions on the list.
Gerald (Jerry) Carter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Dave Poeschel wrote:
>>With Samba 3.0 releases, the master daemons no
>>longer kill their children when they terminate.
>>Was this a purposeful change from 2.2 behavior? (If so why?)
>>This is particularly relevant when managing multiple Samba
>>servers running on a single box (for example, highly available
>>"active-active" Serviceguard configurations on HP-UX).
> I expect it was an intended change but I don't have the
> details. You could probably review the old cvs commit logs
> cheers, jerry
> Samba ------- http://www.samba.org
> Centeris ----------- http://www.centeris.com
> "What man is a man who does not make the world better?" --Balian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
David Collier-Brown, | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb at spamcop.net | -- Mark Twain
More information about the samba-technical