eventscripts: Fix statd-callout update handling
commit2e515f230602116be2a945119d3442d557b81f75
authorMartin Schwenke <martin@meltin.net>
Tue, 28 May 2013 02:01:57 +0000 (28 12:01 +1000)
committerMartin Schwenke <martin@meltin.net>
Tue, 28 May 2013 06:11:47 +0000 (28 16:11 +1000)
tree10b8a31865ac9c42f7b528125e8f8353ad1b1eef
parent529db4d52c36b33e923654c1051017eac90fce38
eventscripts: Fix statd-callout update handling

60.nfs and 60.ganesha touch $statd_update_trigger every time they're
run.  This stops the statd-callout updates from ever being called.

Make this logic self-contained and move it to new function
nfs_statd_update() in the functions file.  Call this in 60.nfs and
60.ganesha with the appropriate update period as the only argument.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reported-by: Poornima Gupte <poornima.gupte@in.ibm.com>
(This used to be ctdb commit 1b5968f6be084590667f4f15ff3bef13ed9a2973)
ctdb/config/events.d/60.ganesha
ctdb/config/events.d/60.nfs
ctdb/config/functions