dhcpcd-discuss

Hi Igor

It has always had this dependency, it was just made more obvious with seccomp. It is already fixed on the git master branch and hopefully a new release over the next few days.

Roy

Sent from Nine
________________________________
From: Igor Šarić <karabaja4@xxxxxxxxx>
Sent: Saturday, 31 October 2020 13:44
To: dhcpcd-discuss@xxxxxxxxxxxx
Subject: dhcpcd 9.3.1 dependency on syslog

Hello,

I noticed dhcpcd 9.3.1 expects the syslog /dev/log socket to be present, otherwise it just refuses to give me a lease (hangs indefinitely). dhcpcd 9.2.0 didn't have this issue.

Normal mode (hangs indefinitely):

~ >> sudo /usr/bin/dhcpcd -4 -B enp2s0
dhcpcd-9.3.1 starting
DUID 00:04:6f:c9:4d:20:33:b8:81:e4:37:ab:38:2c:4a:11:1c:0f
enp2s0: waiting for carrier
ps_ctl_listen: read: Success

In debug mode, it crashes immediately:

~ >> sudo /usr/bin/dhcpcd -d -4 -B enp2s0
dhcpcd-9.3.1 starting
chrooting as dhcpcd to /var/lib/dhcpcd
sandbox: seccomp
Bad system call

Here are the straces:
https://igorsaric.blob.core.windows.net/storage2/strace-normal.log
https://igorsaric.blob.core.windows.net/storage2/strace-debug-mode.log

With syslog running, it works as expected.

If the dependency on syslog was added on purpose, would it be possible to include a nicer error message, instead of just behaving very mysteriously? :)

Thanks for your help!

Regards,

Igor