man/man1m/fmd.1m

         te
 Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved.
 The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
 You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
 When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
 FMD 1M "Nov 17, 2004"
 NAME
fmd - fault manager daemon
 SYNOPSIS

/usr/lib/fm/fmd/fmd [-V] [-f file] [-o opt=val] [-R dir]


 DESCRIPTION

fmd is a daemon that runs in the background on each Solaris system.
fmd receives telemetry information relating to problems detected by the
system software, diagnoses these problems, and initiates proactive self-healing
activities such as disabling faulty components. When appropriate, the fault
manager also sends a message to the syslogd(1M) service to notify an
administrator that a problem has been detected. The message directs
administrators to a knowledge article on Sun's web site,
http://www.sun.com/msg/, which explains more about the problem impact and
appropriate responses.

Each problem diagnosed by the fault manager is assigned a Universal Unique
Identifier (UUID). The UUID uniquely identifes this particular
problem across any set of systems. The fmdump(1M) utility can be used to
view the list of problems diagnosed by the fault manager, along with their
UUIDs and knowledge article message identifiers. The fmadm(1M)
utility can be used to view the resources on the system believed to be faulty.
The fmstat(1M) utility can be used to report statistics kept by the fault
manager. The fault manager is started automatically when Solaris boots, so it
is not necessary to use the fmd command directly. Sun's web site explains
more about what capabilities are currently available for the fault manager on
Solaris.
 OPTIONS

The following options are supported
-f file

Read the specified configuration file prior to searching for any of the
default fault manager configuration files.


-o opt=value

Set the specified fault manager option to the specified value. Fault manager
options are currently a Private interface; see attributes(5) for
information about Private interfaces.


-R dir

Use the specified root directory for all pathnames evaluated by the fault
manager, instead of the default root (/).


-V

Print the fault manager's version to stdout and exit.


 EXIT STATUS

The following exit values are returned:
0

Successful completion


1

An error occurred which prevented the fault manager from initializing, such as
failure to open the telemetry transport.


2

Invalid command-line options were specified.


 FILES
/etc/fm/fmd

Fault manager configuration directory


/usr/lib/fm/fmd

Fault manager library directory


/var/fm/fmd

Fault manager log directory


 ATTRIBUTES

See attributes(5) for descriptions of the following attributes:


ATTRIBUTE TYPE ATTRIBUTE VALUE
Interface Stability Evolving


 SEE ALSO

svcs(1), fmadm(1M), fmdump(1M), fmstat(1M),
syslogd(1M), attributes(5), smf(5)

http://www.sun.com/msg/
 NOTES

The Fault Manager is managed by the service management facility, smf(5),
under the service identifier:
 svc:/system/fmd:default


The service's status can be queried using the svcs(1) command.
Administrators should not disable the Fault Manager service.