Project

General

Profile

Actions

Bug #9470

closed

unbound remotecontrol.conf not rewritten when the file is empty

Added by Jim Pingle over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
DNS Resolver
Target version:
Start date:
04/11/2019
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

If /var/unbound/remotecontrol.conf is empty, it will not be rewritten. The code to write the file checks that the file exists, but not its size.

https://forum.netgate.com/topic/142446/should-unbound-control-work-by-default/2

Actions #1

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Chris Linstruth over 2 years ago

Looks good here. cp /dev/null /var/etc/unbound.conf then a save of the unbound configuration populated the file.

Actions #3

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to Resolved
Actions #4

Updated by Jim Pingle over 2 years ago

  • Target version changed from 2.5.0 to 2.4.4-p3
Actions #5

Updated by Jim Pingle over 2 years ago

  • Status changed from Resolved to Feedback
Actions #6

Updated by Chris Linstruth over 2 years ago

2.4.4-p3 Looks good:

cp /dev/null /var/unbound/remotecontrol.conf
Save unbound configuration
/var/unbound/remotecontrol.conf populated

Actions #7

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF