# default is to not manage Samba
# CTDB_MANAGES_SAMBA=yes
+ # should ctdb manage starting/stopping Winbind service?
++# if left comented out then it will be autodetected based on smb.conf
+ # CTDB_MANAGES_WINBIND=yes
+
# you may wish to raise the file descriptor limit for ctdb
# use a ulimit command here. ctdb needs one file descriptor per
# connected client (ie. one per connected client in Samba)
SAMBA_CLEANUP_PERIOD=10
}
++
++# autodetect use of winbind if not set in config file
++[ -z "$CTDB_MANAGES_WINBIND" ] && {
++ secmode=`testparm -s --parameter-name=security 2> /dev/null`
++ case $secmode in
++ ADS|DOMAIN)
++ CTDB_MANAGES_WINBIND="yes";
++ ;;
++ *)
++ CTDB_MANAGES_WINBIND="no";
++ ;;
++ esac
++}
++
###########################
# periodic cleanup function
periodic_cleanup() {
It is strongly recommended that you set this parameter to "yes" if you intend to use clustered samba.
-It is strongly recommended that you set this parameter to "yes" if you intend to use clustered samba.
+ <h3>CTDB_MANAGES_WINBIND</h3>
+ This is a parameter in /etc/sysconfig/ctdb<br><br>
+ When this parameter is set to "yes" CTDB will start/stop/restart the local winbind daemon as the cluster configuration changes.<br><br>
+ When this parameter is set you should also make sure that winbind is NOT started by default by the linux system when it boots:
+ <pre>
+ chkconfig winbind off
+ </pre>
+
+ Example:
+ <pre>
+ CTDB_MANAGES_WINBIND="yes"
+ </pre>
+
++It is strongly recommended that you set this parameter to "yes" if you
++intend to use clustered samba in DOMAIN or ADS security mode.
+
<!--#include virtual="footer.html" -->