= phenomenon = package ipmitool ships with ipmievd which is like klogd but for ipmi bmc sel/pef. if ipmi is available provide preset soft link to enable the service after first installation.
ipmi - inteligent platform management bmc - baseboard management controller sel - system event log pef - platform event filtering
= background analysis = logging of hardware monitoring, hardware configuration and hardware management configuration changes related events. By default the sysconfig and code uses local system interface (whatever was probed by ipmi_si module) and accesses /dev/ipmi0.
= implementation recommendation = Detect presence of udev devpath IPI000x from acpi/dmi table probes. If the devpath presence indicates IPMI availability provide the soft link to preset in the spec postinstall of first package installation. depends on ticket #1110
This service reads events from the kernel and dumps them into a log? Why wouldn't this be integrated into the journal, or someplace similar?
journal? not the right person to answer. maybe specific hardware availability/dependencies/limited support of oem extensions/limited probing capabilities/default event settings/duplicate logging since the platform itself provides SEL N/V RAM storage or anything.
Clarification below,
The IPMI uses own standard message format (oem extensible) wrapped in various access methods (in-band(kcs,ssif,...), side-band(lan,lanplus), oem, kernel openipmi).
In case of klogd the event producer is kernel. The interface is different then what IPMI uses.
For ipmievd the event producer is any device accessible through the bmc and the kernel provides only layer access methods. Not the message processing.
For the overview of the IPMI architecture see http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf "Figure 2-1, Intelligent Platform Management Logical Devices". The ipmievd is bottom box. The kernel interface is the SYSTEM MESSAGE INTERFACE box on top of bottom box.
The various communication channel might be more readable from "Figure 1-2, IPMI Block Diagram".
And see "Table 16-1, Event Message Reception" within the ipmi enabled system.
We think that this request is similar to ticket #1110 but we'd need more information. We're unsure of what's being requested here similar to the clarity we need for #1110. Since this ticket depends on #1110 we're going to defer until we know the outcome of that ticket.
it's split/dependent ticket since this one does not include kernel module probing but depends on it (#1110) and this one(#1111) is about service and not kernel modules.
and is different package
In today's FESCo meeting, we agreed that FESCo does not believe a package-private solution to this is the correct method. We suggest you file a bug against systemd to get it added to the default preset file.
Login to comment on this ticket.