projects / packages / fence.git / blame
| Commit | Line | Data |
|---|---|---|
| 8e9663d2 | 1 | Summary: I/O fencing system |
| 50db4c12 | 2 | Summary(pl): System barier I/O |
| 8e9663d2 AM |
3 | Name: fence |
| 4 | %define snap 20040625 | |
| 5 | Version: 0.0.0.%{snap}.1 | |
| 6 | Release: 1 | |
| 7 | License: GPL | |
| 8 | Group: Applications/System | |
| 9 | Source0: %{name}.tar.gz | |
| 10 | # Source0-md5: f3f40096cf957c6825ae76cac153d698 | |
| b07b8fdc | 11 | URL: http://sources.redhat.com/cluster/fence/ |
| 8e9663d2 AM |
12 | BuildRequires: awk |
| 13 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
| 14 | ||
| 15 | %define _sbindir /sbin | |
| 16 | ||
| 17 | %description | |
| 50db4c12 JB |
18 | The Fence system does I/O fencing of cluster members. Any member may |
| 19 | join the default fence domain after which it will be fenced if it | |
| 20 | fails without leaving the fence domain cleanly. The lock_dlm GFS lock | |
| 21 | module will not permit GFS to be mounted until the node has joined a | |
| 22 | fence domain. | |
| 8e9663d2 | 23 | |
| 50db4c12 JB |
24 | The fence daemon, fenced, is usually started by running "fence_tool |
| 25 | join". Once started, fenced joins the default fence domain and the | |
| 26 | node is subject to being fenced if it fails. A collection of fence | |
| 27 | agents are used by fenced to interface with hardware devices (usually | |
| 28 | to shut off its path to shared storage or cycle its power source.) | |
| 29 | ||
| 30 | %description -l pl | |
| 31 |