This repository has been archived by the owner on Jan 1, 2021. It is now read-only.
/etc/init.d/tc-config: line 614: /etc/init.d/dhcp.sh: not found #1229
Labels
question
Usability question, not directly related to an error with Boot2Docker
During booting the following error is thrown:
Obviously there shouldn't be any errors during normal boot.
This is caused by the fact that
tc-config
expects/etc/init.d/dhcp.sh
but that file doesn't exist anymore because it's moved to/etc/rc.d/dhcp.sh
during the build. AFAIK this was done in #960. I don't think simply moving this file is the correct solution, which was already kind of hinted at in #960 by @SvenDowideitThe current
tc-config
includes a wrapper to wrap the asyncdhcp.sh
to wait for either an interface with a broadcast address or until a ping succeeds.It will only use this wrapper when either a tiny core extension is loaded during startup using tftplist/httplist or when an NFS or NBD mount is used.
Also, there's an option to disable triggering DHCP entirely from
tc-config
(which will obviously only work when not using any of the above 3 extra options) callednodhcp
.Since by default we don't use any of these but we do want a guarantee that there's a DHCP lease before running other commands I believe we have the following options:
/etc/init.d/dhcp.sp
to not run async (ie changeudhcpc -b
toudhcpd -A <seconds>
)tc-config
to always execute thewait4Server()
function. Sincetc-config
callsbootsync.sh
it'll always be done before our custom actions are executednodhcp
to disable DHCP intc-config
and run eitherudhcpc -A <seconds>
, which blocks/waits for<seconds>
waiting to obtain the lease orwait4Server()
fromtc-config
inbootsync.sh
/bootscript.sh
before running any other custom actionsIf someone has a better idea please let me know :)
The text was updated successfully, but these errors were encountered: