hotplugd.1m (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

hotplugd(1M) hotplugd(1M)

NAME

hotplugd - PCI I/O hotplug (attention button) events daemon

SYNOPSIS

/usr/sbin/hotplugd

logﬁle openmode

DESCRIPTION

The

hotplugd daemon handles PCI I/O hotplug (also known as attention button, AB, or doorbell) events

that are generated by pressing the attention button corresponding to a PCI I/O slot.

Only one attention button event is processed by the system at any point in time. If more than one atten-

tion button is pressed, the events are put in a queue within the kernel.

This daemon invokes

/usr/bin/olrad

to perform the various online addition or replacement opera-

tions (OLAR, OL*) on the slot on which the attention button has been pressed. The daemon does not use

the

-f (override CRA results) option of

olrad.

Normally, this daemon is started by the

/sbin/init.d/pci_olar

startup script at boot time. See

the Daemon Startup subsection for details.

If an attention button is pressed before the startup of the daemon, the event is dropped and no messages

are logged. Also see the DIAGNOSTICS section for messages that are logged in the system log ﬁle or the

hotplugd log ﬁle.

Only users with superuser privileges may use this command to perform OL* functions.

Currently, only the online addition and replacement functions are supported. Online deletion is not sup-

ported.

The blinking of the power LED is not supported on all hardware platforms.

Operands

The following operands are required. See also the Daemon Startup subsection.

logfile Log ﬁle where the daemon will log its messages. The standard output and standard error

of the /usr/bin/olrad

command are also captured in this log ﬁle.

openmode Mode in which to open the logﬁle. It can be one of the following:

append Open the ﬁle in append mode. New log information is appended at the end of

logﬁle .

trunc Open the ﬁle and truncate it. If the logﬁle exists, its length is truncated to 0

and the mode and owner are unchanged.

Daemon Startup

In the normal (and recommended) operation

hotplugd is invoked at boot time through the startup

script, /sbin/init.d/pci_olar

. The startup script reads the conﬁguration ﬁle,

/etc/rc.config.d/pci_olar for the conﬁguration ﬁle variables, HOTPLUGD_LOGFILE

and

HOTPLUGD_MODE, which are assigned to the logﬁle and openmode parameters, respectively. The

installed default values are:

HOTPLUGD_LOGFILE=/var/adm/hotplugd.log

HOTPLUGD_MODE=trunc

To start a new instance of hotplugd with new values for logﬁle and mode, you can do so by stopping the

running instance of hotplugd and manually starting it with the new values.

To have

hotplugd always invoked on startup with the new values, change the values of the

HOTPLUGD_LOGFILE and HOTPLUGD_MODE variables in the conﬁguration ﬁle,

/etc/rc.config.d/pci_olar. At the next boot, hotplugd will be invoked with these new values.

DIAGNOSTICS

Messages in the System Log File

The following messages are logged in the system log ﬁle,

/var/adm/syslog/syslog.log.Ifan

attention button event occurs after the daemon has been terminated following a successful start of the

daemon, the messages are logged in the system log ﬁle.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (4 pages)

PAGE 1
hotplugd(1M) hotplugd(1M) NAME hotplugd - PCI I/O hotplug (attention button) events daemon SYNOPSIS /usr/sbin/hotplugd logfile openmode DESCRIPTION The hotplugd daemon handles PCI I/O hotplug (also known as attention button, AB, or doorbell) events that are generated by pressing the attention button corresponding to a PCI I/O slot. Only one attention button event is processed by the system at any point in time. If more than one attention button is pressed, the events are put in a queue within the kernel.
PAGE 2
hotplugd(1M) hotplugd(1M) Could not allocate memory for PCI I/O Attention Button event A chunk of memory, used for storing the attention button event information, could not be allocated. The event is dropped after the power LED is set to PWR_RAIL mode. That is, the power LED will be set to ON if the power to the slot is ON, or the power LED will be set to OFF if the power to the slot is OFF.
PAGE 3
hotplugd(1M) hotplugd(1M) Could not open the device in the read-write mode. errMsg gives the reason for the error. Error setting close-on-exec flag on /dev/olar file = errMsg Setting the close-on-exec flag on /dev/olar using fcntl() failed. errMsg gives the reason for the error. At times, terminating the daemon with kill -9 may not clear all kernel data structures. If you try to restart the daemon, it may report an error, ioctl(DEV_OLAR_INIT_ABEVENT) Failed.
PAGE 4
hotplugd(1M) hotplugd(1M) #oprnNum - slot( slotId ) - Setting power led to PWR_RAIL mode failed, olar_error_no = olarErrMsg The power LED could not be set to PWR_RAIL mode for the given slotId . olarErrMsg gives the reason for the error. Usage : hotplugd The hotplugd program was invoked with an invalid set of parameters. hotplugd : fork() failed, errno = errMsg hotplugd could not fork itself. errMsg gives the reason for the error.