admfailoverapplication(1M) DG/UX R4.11MU05 admfailoverapplication(1M)
NAME
admfailoverapplication - manage failover application database
SYNOPSIS
admfailoverapplication -o add -h hostname -l local-diskname -r
remote-diskname command
admfailoverapplication -o delete -h hostname -l local-diskname [
command ]
admfailoverapplication -o modify -h hostname -l local-diskname -c
command [ -r new-remote-diskname ] [ newcommand ]
admfailoverapplication -o list [ -qv ]
DESCRIPTION
admfailoverapplication provides operations for manipulating entries
in the failover(4M) application database. The entries in this
database identify the host that the physical disk can be failed over
to/from, the name of the physical disk as it appears on each host,
and the pathname of the script that will be executed when the
physical disk is failed over. A database manager startup script or
command line is an example of an application that can be started by
the failover software. This script is executed by the admfailoverdisk
command and must contain the path to the interpreter to be used, as
the first line (eg., #!/bin/sh ).
When a physical disk is brought online by the admfailoverdisk
command, all application scripts for that physical disk will be
executed. The application script should be capable of handling and
reporting any errors it encounters without the help of the failover
software. The exit status of the application script is not checked
when it is executed.
Operations
add Add a new application command entry to the application
database. If an entry already exists for this command, an
error will result. You must have appropriate privilege to
execute this operation.
delete Delete application command entry from the application
database. If a specific application command is given as an
argument, only that application command entry will be
deleted. Otherwise all application command entries for the
specified hostname and local-diskname will be deleted. You
must have appropriate privilege to execute this operation.
modify Modify the specified application command entry. Either the
remote-diskname or the application command can be modified.
You must have appropriate privilege to execute this
operation.
list List information about application in the failover
database. The list operation reports the following
failover database information to stdout:
the name of the host that disks can be failed over to/from
the name of the physical disk as it appears on the current host
the name of the physical disk as it appears on the remote host
the full path to the user built application command
With the "verbose" format (-v), information is printed in
aligned columns with column headers. With the "quiet"
format (-q) headers are suppressed and each application
entry is printed on a separate line. If both -q and -v be
specified, the output will be in "quiet" format.
Options
The following options must be used with the add, delete, and modify
operations:
-h hostname-path
Name of the host from which the disk will be failed over
from. The hostname must be a valid hostname and must have
an entry in the failover hosts database.
-l local-diskname
Name of the physical disk as it appears on this host. The
diskname must be specified in DG/UX common format for
example, da(hada(),6).
-r remote-diskname
Name of the physical disk as it appears on the remote host.
The diskname must be specified in DG/UX common format for
example, da(hada(),6).
The following option must be used with the modify operation:
-c command
The application command as it appears now in the failover
application database.
The following option can be used with the modify operation
-r remote-diskname
Name of the physical disk as it appears on the remote host.
The diskname must be specified in DG/UX common format for
example, da(hada(),6).
The following options can be used with the list operation
-q Quiet. Produce an unformatted listing with no headers,
fields delimited by a single space.
-v Verbose. Produce a formatted listing with headers and
aligned columns. This option is enabled by default.
EXAMPLE
For this example, assume that on machineA you wish to add an
application entry for a disk module that can be failed over to
machineB. You would add the application to the failover database
using
admfailoverapplication -o add -h machineB -l "da(hada(),8)" \
-r "da(hada(),8)" /usr/bin/myscript
FILES
/etc/failover failover database files
DIAGNOSTICS
Errors
- An attempt was made to add an application entry that already
exists.
- An attempt was made to delete or modify an application entry
that does not exists.
- A hostname value was specified that is not a valid hostname.
- A hostname value was specified for a host that is not in the
failover hosts database.
Exit Codes
0 The operation was successful.
1 The operation was unsuccessful.
2 The operation failed due to access restrictions.
3 There was an error in the command line.
SEE ALSO
sysadm(1M), failoverd(1M), admfailovergiveaway(1M),
admfailoverhosts(1M), admfailovertakeaway(1M), failover(4M),
cap_defaults(5).
NOTES
You must have appropriate privilege to perform all operations except
list. On a generic DG/UX system, appropriate privilege is granted by
having an effective UID of 0 (root). See the appropriate_privilege(5)
man page for more information.
On a system with DG/UX information security, appropriate privilege is
granted by having one or more specific capabilities enabled in the
effective capability set of the user. See cap_defaults(5) for the
default capabilities for this command.
Licensed material--property of copyright holder(s)