Compare commits

...

2 Commits

Author SHA1 Message Date
Dustin 9cf4111af7 gw0: Set dhcpcd_nodev
Disabling device management in `dhcpcd` avoids the "received NULL
device" log spam.
2018-07-20 17:47:04 -05:00
Dustin da2d73b676 roles/dhcpcd: Disable device management module
Today I realized that `dhcpcd` has been logging several hundred thousand
of these messages every second:

    libudev: received NULL device

This was causing both `dhcpcd` and `systemd-journald` to consume 100%
CPU.

I am not entirely sure what a "device management" module is in the
context of `dhcpcd`, but it does not seem to be required. Setting the
`nodev` option in `dhcpcd.conf` suppresses the messages, and seems to
have no effect on the operation of the daemon.
2018-07-20 17:46:47 -05:00
3 changed files with 7 additions and 0 deletions

View File

@ -61,6 +61,7 @@ network:
addr: 172.30.0.241 addr: 172.30.0.241
prefix: 28 prefix: 28
dhcpcd_nodev: true
dhcpcd_send_hostname: false dhcpcd_send_hostname: false
dhcpcd_ntp_servers: false dhcpcd_ntp_servers: false
dhcpcd_noipv4: true dhcpcd_noipv4: true

View File

@ -11,3 +11,4 @@ dhcpcd_noipv4ll: false
dhcpcd_noipv4: false dhcpcd_noipv4: false
dhcpcd_noipv6rs: false dhcpcd_noipv6rs: false
dhcpcd_interfaces: [] dhcpcd_interfaces: []
dhcpcd_nodev: false

View File

@ -1,5 +1,10 @@
# A sample configuration for dhcpcd. # A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details. # See dhcpcd.conf(5) for details.
{% if dhcpcd_nodev %}
# Disable device management to avoid "libudev: received NULL device" log spam
nodev
{% endif %}
# Allow users of this group to interact with dhcpcd via the control socket. # Allow users of this group to interact with dhcpcd via the control socket.
{% if dhcpcd_controlgroup is defined %} {% if dhcpcd_controlgroup is defined %}