Bug 233229

Summary: dns/unbound 1.8.1 logfile log-time-ascii shows no updated timestamp
Product: Ports & Packages Reporter: p5B2EA84B3
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed FIXED    
Severity: Affects Some People CC: jaap
Priority: --- Flags: koobs: maintainer-feedback? (jaap)
Version: Latest   
Hardware: Any   
OS: Any   
Bug Depends on: 233796    
Bug Blocks:    
Attachments:
Description Flags
temorary patch none

Description p5B2EA84B3 2018-11-14 20:22:12 UTC 
Having set log-time-ascii: yes in unbound.conf 
the timestamps in the logfile shows the time when i.e. unbound-control reload has been run in each line. The timestamps are not updated.
Comment 1 Jaap Akkerhuis 2018-11-22 10:23:14 UTC 
I checked with upstream, this is a known issue and waiting for the next release. A workaround is to use syslog.

For the impatients, the fix is already in the svn repository <https://nlnetlabs.nl/svn/unbound/> and on github <https://github.com/NLnetLabs/unbound>.

    jaap
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2018-11-22 11:55:26 UTC 
(In reply to jaap from comment #1)

What is the resolution of this issue? 

1) Upstream commit added as patch to the existing port until next release?
2) Add pkg-message or comment in configuration file sample mentioning the "known issue" ?
3) Something else?
4) Close -> Rejected (WONTFIX) ?

Can you also add any upstream bug reports / pull request / commit url's where applicable
Comment 3 Jaap Akkerhuis 2018-11-26 14:40:27 UTC 
(In reply to Kubilay Kocak from comment #2)

The fix is in the repositories mentioned but not released. Normally I wait for the officially release, that prevents creating a temporary patch which needs to be taken out later.
Comment 4 Jaap Akkerhuis 2018-11-26 14:41:48 UTC 
Created attachment 199570 [details]
temorary patch

Temporary patch
Comment 5 Jaap Akkerhuis 2018-12-05 09:45:41 UTC 
I just send in an uprade of unbound, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233796 which should fix this problem.

Therefore we can close this ticket.