Skip to content

Add Windows Support for the .logstash-forwarder file from overwrite to rewrite #487

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

Closed
wants to merge 1 commit into from
Closed

Conversation

aldofunes
Copy link

This code was taken from Pull Request 273

I am using the latest logstash-forwarder version though, because the implementation of Pull Request 273 fails with this version.

I am fairly new to GitHub, so here is the message from sdgroot:

Here is what
Due to the use of the 'defer' keyword, file handles were kept open too long. This resulted in the error 'The process cannot access the file because it is being used by another process.'.

Another addition is for opening the file .logstash-forwarder. Initially this file will not exist. The Registar for Windows assumes this file exists. Therefore we explicitly tell the OS to create the file when it doesn't exist yet.

See also https://groups.google.com/forum/#!topic/logstash-users/oFDcoGj8Qtc

@justmara
Copy link

justmara commented Aug 3, 2015

there is #272 wich is already rebased to new code and is still working.

@ruflin
Copy link

ruflin commented Oct 6, 2015

This should be fixed in filebeat (next version of logstash-forwarder) with https://github.com/elastic/filebeat/pull/43 and https://github.com/elastic/filebeat/pull/45

@ruflin
Copy link

ruflin commented Oct 7, 2015

As the next release of logstash-forwarder will be filebeat, I will close this issue based on the comment above. In case the issue still exists in filebeat, please reopen or open a new issue directly in the filebeat repo.

@ruflin ruflin closed this Oct 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants