unbound: control files not copied to /var/lib with manual configuration
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @EricLuehrsen
Environment: OpenWrt 22.03.2
Description:
I have a configuration with manual_conf set to 1 and remote-control enabled. In commit 658c27ea97, the copy was changed from doing cp -p /etc/unbound/* to two more specific copies for *.conf and root.* with further files such as those needed for remote control only copied in the unbound_control() function. This function isn't called if a manual configuration is enabled. The effect of this is that unbound won't start unless I manually copy the extra files over.
Possible Solution:
Something like the following would probably work. Was there other reasons to limit the copied files?
if [ $UB_B_MAN_CONF -eq 0 ] ; then
cp -p $UB_ETCDIR/*.conf $UB_VARDIR/
cp -p $UB_ETCDIR/root.* $UB_VARDIR/
else
cp -p $UB_ETCDIR/* $UB_VARDIR/
fi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the OpenWrt unbound startup script containing unbound_control() and the UB_B_MAN_CONF, UB_ETCDIR, and UB_VARDIR handling; compare it with commit 658c27ea97. Test a manual_conf=1 configuration with remote-control enabled and verify that unbound starts without manually copying the additional control files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100