search for: ctdb_max_open_files

.../nodes # List of public addresses for providing NAS services. No default. CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses # What services should CTDB manage? Default is none. # CTDB_MANAGES_SAMBA=yes # CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_NFS=yes # Raise the file descriptor limit for CTDB? # CTDB_MAX_OPEN_FILES=10000 # Default is to use the log file below instead of syslog. CTDB_LOGGING=file:/var/log/log.ctdb # Default log level is NOTICE. Want less logging? CTDB_DEBUGLEVEL=DEBUG # Set some CTDB tunable variables during CTDB startup? # CTDB_SET_TDBMutexEnabled=0 CTDB_NFS_CALLOUT=/etc/ctdb/nfs-ganesha...

...now hardwired. Symlinks can be used if necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending on distro). > # Default is to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb ctdb.conf: [logging] location = fi...

...necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending on distro). > # Default is to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb c...

...; # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending on distro). > # Default is to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log...

...necessary. > # What services should CTDB manage? Default is none. > # CTDB_MANAGES_SAMBA=yes > # CTDB_MANAGES_WINBIND=yes > CTDB_MANAGES_NFS=yes Gone. Now just enable the event scripts. > # Raise the file descriptor limit for CTDB? > # CTDB_MAX_OPEN_FILES=10000 Gone. Either do the right thing in the systemd unit file or put a ulimit command in /etc/sysconfig/ctdb or /etc/default/ctdb (depending on distro). > # Default is to use the log file below instead of syslog. > CTDB_LOGGING=file:/var/log/log.ctdb c...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...

...een removed * The CTDB_SHUTDOWN_TIMEOUT configuration variable has been removed As with other daemons, if ctdbd does not shut down when requested then manual intervention is required. There is no safe way of automatically killing ctdbd after a failed shutdown. * CTDB_SUPPRESS_COREFILE and CTDB_MAX_OPEN_FILES configuration variable have been removed These should be setup in the systemd unit/system file or, for SYSV init, in the distribution-specific configuration file for the ctdb service. * CTDB_PARTIALLY_ONLINE_INTERFACES incompatibility no longer enforced 11.natgw and 91.lvs will no long...