dhcpcd-discuss

Hi

On 07/06/2014 12:32, Peter Mattern wrote:
> Hello.
>
> So once more a delayed answer; this time I ran into
> https://github.com/archlinuxarm/PKGBUILDs/issues/861 which turned into
> a problem as my card reader had decided to fail some days ago and
> systemd's rescue and emergency target seem to rely on cgroups. Anyway
> it took some time to get the device running again...
>
> The good news is that it works now. Extract from the serial console

Great!

> Yet there remain some things strange at least to me:
>
> First and trivial, those "marker numbers" introduced by patching
> dhcp6.c can now only be seen on the serial console but no longer in
> systemd's journal. I did a fresh install due to the problem stated
> above. But I thought that everything was configured and compiled as
> before and thus have no clue about that different logging behaviour.
> 'debug' is set in dhcpcd.conf. If you should have any idea...

Sure
dhcpcd outputs everything via syslog, but the marker numbers just go via 
stderr.
dhcpcd configures syslog to also output to the console via stderr.
I would guess that systemd no longer logs stderr and just syslog

> Second, you mentioned that SO_REUSEPORT was introduced in 3.9. But
> Arch Linux i686 / x86_64, where the problem never appeared, is running
> 3.14.5 and Arch Linux ARM is using a fork from
> https://github.com/linux-sunxi/linux-sunxi, right now 3.4.79.

Ah, so the running kernel is 3.4 but you have compiled it against 3.9 
headers or newer?
Well, that does explain the problem. Normally you match the kernel 
headers to the installed version.

> If this should be of interest, I'm attaching an archive that contains
> the files Arch Linux's build system is using to build the x86_64
> Kernel. Upstream Kernel and patches can be seen from the source
> variable in script PKGBUILD. As for Arch Linux ARM, the relevant
> PKGBUILD and config files can be found here:
> https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-sun7i.

Well, it sounds like an Arch Linux issue and not really something dhcpcd 
or I should try and fix.
At least we've worked around it though and you're up and running!

Roy