Installation guide
<logging>
<!-- turning on per-subsystem debug logging -->
<logging_daemon name="corosync" debug="on" />
<logging_daemon name="fenced" debug="on" />
<logging_daemon name="qdiskd" debug="on" />
<logging_daemon name="rgmanager" debug="on" />
<logging_daemon name="dlm_controld" debug="on" />
<logging_daemon name="gfs_controld" debug="on" />
</logging>
...
</cluster>
For a list of the logging daemons for which you can enable logging as well as the additional logging
options you can configure for both global and per-daemon logging, refer to the cluster. co nf(5)
man page.
7.8. Configuring nfsexport and nfsserver Resources
This section describes the issues and considerations to take into account when configuring an
nfsexpo rt or an nfsserver resource.
The nfsexpo rt resource agent works with NFSv2 and NFSv3 clients. When using nfsexpo rt, you
must do the following:
Ensure that nfs and nfslo ck are enabled at boot.
Add R P C NFSDAR G S= "-N 4 " to the /etc/sysco nfi g /nfs file on all cluster nodes. The "-N 4 "
option prevents NFSv4 clients from being able to connect to the server.
Add ST AT D AR G S= "-H /usr/sbi n/cl unfslo ck" to the /etc/sysco nfi g /nfs file on all
cluster nodes.
Add nfsl o ck= "1" to the servi ce component in the cluster. co nf file.
Structure your service as follows:
<service nfslock="1" ... >
<fs name="myfs" ... >
<nfsexport name="exports">
<nfsclient ref="client1" />
<nfsclient ref="client2" />
...
</nfsexport>
</fs>
<ip address="10.1.1.2" />
...
</service>
The nfsserver resource agent works with NFSv3 and NFSv4 clients. When using nfsserver, you
must do the following:
Ensure that nfs and nfslo ck are disabled at boot
Ensure that nfsl o ck= "1" is not set for the service.
Structure your service as follows:
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
126