https://bugzilla.redhat.com/show_bug.cgi?id=634736
Fredy Neeser <nfd(a)zurich.ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nfd(a)zurich.ibm.com
--- Comment #23 from Fredy Neeser <nfd(a)zurich.ibm.com> ---
(In reply to Adam Williamson (Red Hat) from comment #19)
Many thanks to Adam for his writeup (see link in comment #22)!
The udev rule worked for me, too (on a Fedora 20 I had just upgraded from 19),
after noting the error in the sysctl.d manpage:
sysctl.d manpage notes:
"Many sysctl parameters only become available when certain kernel modules
are loaded. Modules are usually loaded on demand, e.g. when certain hardware
is plugged in or network brought up. This means that
systemd-sysctl.service(8) which runs during early boot will not configure
such parameters if they become available after it has run. To set such
parameters, it is recommended to add an udev(7) rule to set those parameters
when they become available."
The example udev rule given for bridging is:
/etc/udev/rules.d/99-bridge.conf:
^
|
This should be 99-bridge.rules
ACTION=="add", SUBSYSTEM=="module",
KERNEL=="bridge",
RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/bridge"
Of course, udev will ignore a udev rules file that doesn't have a .rules
extension ...
Should we open a bug against the sysctl.d manpage?
(see Example 2, /etc/udev/rules.d/99-bridge.conf)
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.