dhcpcd-discuss

On 17/10/2013 19:39, Joseph Felps wrote:
> Hello, I'm using dhcpcd 6.1.0 on a new LFS build on Linux kernel
> 3.11.4.  Some of the dhcpcd-run-hooks don't seem to be running at
> startup.  Here is a log of dhcpcd startup:
>
> Oct 17 08:18:37 LFS-PC dhcpcd[434]: version 6.1.0 starting
>  Oct 17 08:18:37 LFS-PC dhcpcd[434]: script_runreason:
> /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 127
> Oct 17 08:18:37 LFS-PC dhcpcd[434]: script_runreason:
> /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 127
> Oct 17 08:18:37 LFS-PC dhcpcd[434]: eth0: waiting for carrier
>  Oct 17 08:18:38 LFS-PC dhcpcd[434]: eth0: carrier acquired
> Oct 17 08:18:38 LFS-PC dhcpcd[434]: script_runreason:
> /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 127
> Oct 17 08:18:38 LFS-PC dhcpcd[434]: eth0: soliciting an IPv6 router
>  Oct 17 08:18:38 LFS-PC dhcpcd[434]: eth0: soliciting a DHCP lease
> Oct 17 08:18:41 LFS-PC dhcpcd[434]: eth0: offered 192.168.1.110 from
> 192.168.1.1
> Oct 17 08:18:45 LFS-PC dhcpcd[434]: eth0: leased 192.168.1.110 for
> 86400 seconds
>  Oct 17 08:18:45 LFS-PC dhcpcd[434]: eth0: adding host route to
> 192.168.1.110 via 127.0.0.1
> Oct 17 08:18:45 LFS-PC dhcpcd[434]: eth0: adding route to
> 192.168.1.0/24 [1]
> Oct 17 08:18:45 LFS-PC dhcpcd[434]: eth0: adding default route via
> 192.168.1.1
>  Oct 17 08:18:45 LFS-PC dhcpcd[434]: script_runreason:
> /lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 127
> Oct 17 08:18:45 LFS-PC dhcpcd[434]: forked to background, child pid
> 439
>
> I can't figured out the reason, but if I go back to Linux kernel 3.8
> everything runs fine.

Well, dhcpcd uses posix_spawn(3) when available.
I think this uses a kernel feature which could be broken in.
Try enabling the emulation posix_spawn with ./configure 
--without-posix_spawn
Other than that, it could be dhcpcd can't see the script 
/lib/dhcpcd/dhcpcd-run-hooks

Try putting a command at the top of the script to echo to the console.

Thanks

Roy