Copyright (c) 2009, 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]
/usr/lib/ldoms/ldmad
The ldmad daemon is part of the framework that enables Logical Domain agents to run on a Logical Domain. A Logical Domain agent is a component that interacts with the control domain for providing features or information.
ldmad is responsible for running agents on a Logical Domain and must be enabled to ensure proper functionality of all features provided by the domain manager on the control domain. It is started at boot time and has no configuration options.
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE ATTRIBUTE VALUE |
| Interface Stability Unstable |
svcs(1), svcadm(1M), syslog(3C), syslog.conf(4), attributes(5), smf(5)
ldmad uses syslog(3C) to report status and error messages. All of the messages are logged with the LOG_DAEMON facility. Error messages are logged with the LOG_ERR and LOG_NOTICE priorities, and informational messages are logged with the LOG_INFO priority. The default entries in the /etc/syslog.conf file log all of the ldmad error messages to the /var/adm/messages log.
The ldmad service is managed by the service management facility, smf(5), under the service identifier:
svc:/ldoms/agents:default
Administrative actions on this service, such as enabling, disabling, or requesting restart can be performed using svcadm(1M). The service's status can be queried using the svcs(1) command.