Is this a new report?
Yes
System Info
Void 6.18.33_1 x86_64 AuthenticAMD notuptodate rF
Package(s) Affected
dhcpcd-10.3.1_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Messages must not be duplicated and must have the correct priority.
Actual behaviour
The logs are being duplicated.
As I understand it, because log/run is redundant since dhcpcd already does it and does it better (correctly sets message priorities). If I understand correctly, log/run is created automatically, and it needs to be replaced with a stub? Or is there an option in the build rules that disables this behavior?
svlogtail:
2026-05-31T17:35:27.92734 daemon.info: May 31 20:35:27 dhcpcd[17005]: received SIGTERM, stopping
2026-05-31T17:35:27.92737 daemon.info: May 31 20:35:27 dhcpcd[17005]: amn0: removing interface
2026-05-31T17:35:27.92738 daemon.notice: May 31 20:35:27 dhcpcd: received SIGTERM, stopping
2026-05-31T17:35:27.92739 daemon.notice: May 31 20:35:27 dhcpcd: amn0: removing interface
2026-05-31T17:35:27.93134 daemon.info: May 31 20:35:27 dhcpcd[17005]: wlp2s0: removing interface
2026-05-31T17:35:27.93138 daemon.notice: May 31 20:35:27 dhcpcd: wlp2s0: removing interface
2026-05-31T17:35:27.93318 daemon.info: May 31 20:35:27 dhcpcd[17005]: enp1s0: removing interface
2026-05-31T17:35:27.93321 daemon.notice: May 31 20:35:27 dhcpcd: enp1s0: removing interface
2026-05-31T17:35:27.94649 daemon.info: May 31 20:35:27 dhcpcd[17005]: dhcpcd exited
2026-05-31T17:35:27.94652 daemon.notice: May 31 20:35:27 dhcpcd: dhcpcd exited
dhcpcd-eth0 is also susceptible to this problem.
Steps to reproduce
sv restart dhcpcd
svlogtail
Is this a new report?
Yes
System Info
Void 6.18.33_1 x86_64 AuthenticAMD notuptodate rF
Package(s) Affected
dhcpcd-10.3.1_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
Messages must not be duplicated and must have the correct priority.
Actual behaviour
The logs are being duplicated.
As I understand it, because
log/runis redundant sincedhcpcdalready does it and does it better (correctly sets message priorities). If I understand correctly,log/runis created automatically, and it needs to be replaced with a stub? Or is there an option in the build rules that disables this behavior?svlogtail:dhcpcd-eth0is also susceptible to this problem.Steps to reproduce
sv restart dhcpcdsvlogtail