search for: disablescript

Hi all Thanks for your attention. CTDB manages NICs with event scripts. Virtual IP attaches on a NIC as a secondary IP. When noticing the NIC down, CTDB will pull it up. Does any one know how to disable the action? I do not want CTDB pull any NIC up. Does the command 'ctdb disablescript 10.interface' has any unexpected effect? Thanks. ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或...

...e: > Thanks for your attention. CTDB manages NICs with event scripts. > Virtual IP attaches on a NIC as a secondary IP. When noticing the NIC > down, CTDB will pull it up. Does any one know how to disable the > action? I do not want CTDB pull any NIC up. Does the command 'ctdb > disablescript 10.interface' has any unexpected effect? 10.interface actually removes/adds public IP addresses from/to interfaces. So, without this script CTDB's public IP addresses will not work. There is no supported way to disable the behaviour of pulling up interfaces. Why do you want to want to d...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...d compatibility but the output format has been > cleaned up > > "ctdb event run" replaces "ctdb eventscript" > > "ctdb event script enable" replaces "ctdb enablescript" > > "ctdb event script disable" replaces "ctdb disablescript" > > The new command "ctdb event script list" lists event scripts. > > * CTDB's back-end for running event scripts has been replaced by a > separate, long-running daemon ctdbd_eventd. > > * Running ctdb interactively will log to stderr > > * CTDB lo...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...tter is maintained for backward compatibility but the output format has been cleaned up "ctdb event run" replaces "ctdb eventscript" "ctdb event script enable" replaces "ctdb enablescript" "ctdb event script disable" replaces "ctdb disablescript" The new command "ctdb event script list" lists event scripts. * CTDB's back-end for running event scripts has been replaced by a separate, long-running daemon ctdbd_eventd. * Running ctdb interactively will log to stderr * CTDB logs now include process id for each proces...

...ompatibility but the output format has been > cleaned up > > "ctdb event run" replaces "ctdb eventscript" > > "ctdb event script enable" replaces "ctdb enablescript" > > "ctdb event script disable" replaces "ctdb disablescript" > > The new command "ctdb event script list" lists event scripts. > > * CTDB's back-end for running event scripts has been replaced by a > separate, long-running daemon ctdbd_eventd. > > * Running ctdb interactively will log to stderr > > * CTD...