winbind startup script [was Re: svn commit: samba r3708 - in branches/SAMBA_3_0/source/smbd: .]

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Volker.Lendecke at SerNet.DE wrote:
| On Fri, Nov 12, 2004 at 03:51:44PM -0600, Gerald (Jerry) Carter wrote:
|
|>on a standalone server or a Samba DC with no trusts.
|>So then do we lay the burden on the admin to enable
|>the init script ?  That's an acceptable answer to me.
|
|
| What would be a reason not to run winbind on a
| standalone server or lonely DC? Winbind there enables
| local groups, so it actually gains you something even in
| those simple setups.
|
| Don't get me wrong -- I'm not strongly advocating it,
| but I don't see how winbind should disturb any setup.

Ahhh volker....you know that the number of rule of
systems administration is don't run anything you
don't use.  :-)

I'm not saying that winbindd would be valueable on such
systems (well local groups on a standalone server doesn't
make sense).  All I'm saying is that the current method
of always starting winbindd and letting the daemon exit
if is has not been configured doesn't work anymore.
I'm looking for an alternative solution for packaging.

Apparently we'll just assume the sysadmin is smart
enough not to start things he/she doesn't need and/or use.



cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBlTOvIR7qMdg1EfYRApcAAJ4tmI0suiRX/clLKd9+sl06qOkm9QCgr4MT
EJbb9xMbnJTFRsY6ItaNilI=
=HfEh
-----END PGP SIGNATURE-----