Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-w always leave empty files #11

Closed
bortzmeyer opened this issue Jul 15, 2017 · 2 comments
Closed

-w always leave empty files #11

bortzmeyer opened this issue Jul 15, 2017 · 2 comments
Assignees

Comments

@bortzmeyer
Copy link

dnstpa works fine for output on the screen but -w always leave me with empty files.

I tried to SIGHUP the program, to stop it with Control-C, send thousands of requests to get a buffer flush, and in all cases, the output file is created but it is empty.

@cmikk cmikk self-assigned this Jul 25, 2017
@cmikk
Copy link
Member

cmikk commented Jul 25, 2017

Greetings,

I am not able to reproduce this behavior in my testing setup. What versions of golang-dnstap and golang-framestream are you using? There have been a few recent bug fixes in both packages.

Also, are you seeing the message:

dnstap.FrameStreamSockInput: accepted a socket connection

logged when you run dnstap?

@bortzmeyer
Copy link
Author

Indeed, I did not get the message "accepted a socket connection", it works only once with Unbound, I have to restart it if I want dnstap to receive data. Strange but it seems -w is not responsible. Sorry for the false alarm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants