3 Summary: I/O fencing system
6 Version: 0.0.0.%{snap}.1
9 Group: Applications/System
10 Source0: %{name}.tar.gz
11 # Source0-md5: f3f40096cf957c6825ae76cac153d698
12 URL: http://sources.redhat.com/cluster/
14 BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n)
16 %define _sbindir /sbin
19 The Fence system does I/O fencing of cluster members. Any member may join the default fence domain after which it will be fenced if it fails without leaving the fence domain cleanly. The lock_dlm GFS lock module will not permit GFS to be mounted until the node has joined a fence domain.
21 The fence daemon, fenced, is usually started by running "fence_tool join". Once started, fenced joins the default fence domain and the node is subject to being fenced if it fails. A collection of fence agents are used by fenced to interface with hardware devices (usually to shut off its path to shared storage or cycle its power source.)
28 --incdir=%{_includedir} \
29 --kernel_src=%{_kernelsrcdir} \
38 rm -rf $RPM_BUILD_ROOT
41 DESTDIR=$RPM_BUILD_ROOT
44 rm -rf $RPM_BUILD_ROOT
47 %defattr(644,root,root,755)
48 %attr(755,root,root) %{_sbindir}/*