Summary: | systemd-sysctl improperly parses paths | ||
---|---|---|---|
Product: | systemd | Reporter: | David Ford <david+bugs.freedesktop.org> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
David Ford
2014-04-15 06:02:54 UTC
AFAICT, sysctl replaces '.' with '/', and '/' with '.'. So it'll write /proc/sys/net/ipv4/conf/enp3s0.200/forwarding Do you have a file with a dot in the name? it's posted as the first section in my report. Where exactly? # cat 99-sysctl.conf net.ipv4.conf.enp3s0/200.proxy_arp_pvlan=1 net.ipv4.conf.enp3s0/200.forwarding=1 net.ipv4.conf.enp3s0/100.forwarding=1 net.ipv4.conf.enp5s0.forwarding=1 sysctl -p /etc/sysctl.d/99-sysctl.conf will parse this correctly. systemd-sysctl will not parse the first three lines correctly. > net.ipv4.conf.enp3s0/200.proxy_arp_pvlan=1
The question is how is the *file* that sysctl writes to called?
exactly opposite the conf file syntax. e.g.: /proc/sys/net/ipv4/conf/enp3s0.200/proxy_arp_pvlan So you are saying that the classic sysctl tool actually maps "." to "/" and "/" to "." in the fs? How incredibly awful. i'll agree, it turned out to be awkward, but it's the standard we've had for two decades :} |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.