https://bugzilla.redhat.com/show_bug.cgi?id=634736
--- Comment #42 from Edgar Hoch <edgar.hoch(a)ims.uni-stuttgart.de> ---
I agree that forking "sysctl" for each loaded module induce much unnecessary
overhead. So we need a better solution.
I think it may be too complicated for an ordinary user - and for an ordinary
administrator too - to write udev rules when he just want to change the value
of a parameter. udev rules are much more complex than a single parameter
assignment.
I think that there should be a tool with a simple user interface like sysctl,
which users and admins can use to read, set and change parameters of the
system. It may generate udev rule files instead of sysctl config files, that
would be ok. It should have at least a cli, but some gui (maybe combined with
other configuration tools) would be nice too.
The tool should support temporary changes of the parameters (to the running
system, lost after reboot) and permanant changes (changes files in /etc/...) -
preferred by the same tool.
There should also be some reasonable defaults for frequent use cases. I think
bridges with a vm (kvm, libvirt) with external ip addresses (not nat) is a
typical case. virsh is no help for this case (see bug #1134569).
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=zXYeIdLzDK&a=cc_unsubscribe