Description of problem:
When overriding the parameters for
RHEL 5: udevcontrol max_childs=X
RHEL 6: udevadm control --max-childs=X
RHEL 7: udevadm control --children-max=X
either on the command line or via kernel boot parameters there is no way
to show the currently configured value once the system is fully booted.
Version-Release number of selected component (if applicable):
RHEL 5, 6 and 7
Steps to Reproduce:
RHEL 5: # udevcontrol max_childs=7
RHEL 6: # udevadm control --max-childs=7
RHEL 7: # udevadm control --children-max=7
There is no way to read the currently set value.
No command option available to show the actual used value.
Create a command option for udevcontrol/udevadm to show the running configuration.
As an alternative:
Make the information available in /proc/<process_id>
As the preferred option:
Make the actual configured udev timeout parameter visible.
udevadm and udevd interaction is only one directional, meaning that udevadm only sends control command to udev daemon, but no data is returned back from the daemon to client.
For now I've implemented change that introduces new option for udevadm control and udevd upon receiving new type of control message logs current value of children_max parameter on INFO log level, hence message is by default visible in system log.
Would above solution satisfy this RFE?
That solution would not satisfy the RFE as logs are purged automatically and the control messages with it.
(In reply to Stefan Meyer from comment #4)
> That solution would not satisfy the RFE as logs are purged automatically and
> the control messages with it.
I've reworked my initial implementation and proposed it upstream, but PR was rejected. However, we will address this issue upstream, but approach will be very different from my solution. Unfortunately, it won't be possible to backport new fix to RHEL6. I will clone this bug for RHEL7 and close this one.