File 0015-Medium-exportfs-Make-unlock_on_stop_defaul... of Package resource-agents

Overview Repositories Revisions Requests Users Attributes Meta

File 0015-Medium-exportfs-Make-unlock_on_stop_default-1-bnc-86.patch of Package resource-agents (Revision 994afb21beaae4962b34e642a469014d)

Currently displaying revision 994afb21beaae4962b34e642a469014d , Show latest

From e1e6781ef4930d4a9772ee1428dde8f435776267 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Kristoffer=20Gr=C3=B6nlund?= <krig@koru.se>
Date: Mon, 10 Mar 2014 12:03:55 +0100
Subject: [PATCH] Medium: exportfs: Make unlock_on_stop_default=1 (bnc#864263)

The resource agent should really release all locks which the NFS server
holds when stopping the resource. When this option was introduced, the
default was kept as 0 for compatibility reasons with legacy kernels,
existing users and non-Linux systems.

This is a proposal to make 1 the default. In most cases, this is the
desired behavior, and not setting this option can lead to unexpected
failures.

Original changeset that introduced this parameter: 612559c9
---
 heartbeat/exportfs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/heartbeat/exportfs b/heartbeat/exportfs
index 0c6d0921ccef..5ed26754f535 100755
--- a/heartbeat/exportfs
+++ b/heartbeat/exportfs
@@ -14,7 +14,7 @@
 . ${OCF_FUNCTIONS_DIR}/ocf-shellfuncs
 
 # Defaults
-OCF_RESKEY_unlock_on_stop_default=0
+OCF_RESKEY_unlock_on_stop_default=1
 OCF_RESKEY_wait_for_leasetime_on_stop_default=0
 OCF_RESKEY_rmtab_backup_default=".rmtab"
 
-- 
1.8.4.5

Places

File 0015-Medium-exportfs-Make-unlock_on_stop_default-1-bnc-86.patch of Package resource-agents (Revision 994afb21beaae4962b34e642a469014d)

Places