Datasheet
“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 322 — #348
i
i
i
i
i
i
i
i
. Device is already initialized and will be skipped.
* Hotplug event will be created for the device.
W Device is not on the whitelist and will be skipped.
B Device is on the blacklist and will be skipped.
14.8 Error Analysis
14.8.1 Log Files
Unless otherwise specified, hotplug only sends a few important mes-
sages to syslog. To obtain more information, set HOTPLUG_DEBUG=yes.
If you set this variable to the value max, every shell command is logged
for all hotplug scripts. This means that /var/log/messages in which
syslog stores all the messages will be much larger. As syslog is not
launched during the boot process until after hotplug and coldplug,
it is possible, however, for the first messages not to be logged. If these
messages are important to you, specify a different log file via the vari-
able HOTPLUG_SYSLOG. Information about this topic is contained in
/etc/sysconfig/hotplug.
14.8.2 Boot Problems
If a computer hangs during the boot process, disable hotplug or
coldplug by entering NOHOTPLUG=yes or NOCOLDPLUG=yes, respec-
tively, at the boot prompt. When the system is up and running, reenable
hotplug by entering the command rchotplug start.
To find out whether a particular module loaded by hotplug is responsi-
ble for the problem, enter HOTPLUG_TRACE=<N> at the boot prompt. The
names of all the modules are then output one after another on the screen
until after N seconds they are actually loaded. You cannot intervene while
this is going on.
14.8.3 The Event Recorder
The script /sbin/hotplugeventrecorder is called for each event by
/sbin/hotplug and sbin/hotplug-stopped. If a directory /events
exists, all hotplug events are stored as individual files in this directory.
322 14.8. Error Analysis










