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

Add Windows support #674

Merged
merged 150 commits into from
Oct 8, 2015
Merged

Add Windows support #674

merged 150 commits into from
Oct 8, 2015

Conversation

nurse
Copy link
Contributor

@nurse nurse commented Sep 16, 2015

okahashi117 and others added 30 commits July 12, 2013 20:17
cool.io 1.2.0
(use in future)
(use in future)
Singleton class seems to prevent GC and make TailWatcher to be
explicitly closed, which is dangerous because of multithreads
as the comment of close_watcher says.
@nurse
Copy link
Contributor Author

nurse commented Sep 29, 2015

@sodabrew thanks for info.
now CI becomes green! (with allow failure 2.1 x86)

@repeatedly
Copy link
Member

@tagomoris @sonots @frsyuki Check this PR. I have a plan to merge this PR and master branch will be for v0.14 development, e.g. nanosecond, SocketManager, ServerEngine.

@@ -15,6 +15,8 @@
# ignore setup error on Win or similar platform which doesn't support signal
end
require 'cool.io'

$platformwin = /mswin|mingw/ === RUBY_PLATFORM
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From sada's comment on serverengine, how about using this approach like Fluent.on_windows? ? > treasure-data/serverengine#26 (comment)

We have fluent/env.rb so this file seems good place.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed

@@ -65,8 +66,20 @@ def open(&block)
end

def mv(path)
File.rename(@path, path)
@path = path
if defined?(Windows)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fluent.windows? is better?

@repeatedly
Copy link
Member

Commented. The correctness of windows related code relies on patch!

@repeatedly
Copy link
Member

@tagomoris @frsyuki @sonots Are there any concerns? I want to merge this PR before merging nano-second support.

op.on('--reg-winsvc-fluentdopt OPTION', "specify fluentd option paramters for Windows Service. (Windows only)") {|s|
opts[:fluentdopt] = s
}

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about showing above windows-only options only when Fluentd.windows? is true?

@frsyuki
Copy link
Member

frsyuki commented Oct 6, 2015

Great job 👍
I added 2 comments.

@repeatedly
Copy link
Member

If there is no concerns, I will merge this PR tomorrow!

repeatedly added a commit that referenced this pull request Oct 8, 2015
@repeatedly repeatedly merged commit f537195 into master Oct 8, 2015
@nurse nurse deleted the windows branch May 26, 2016 04:45
@gmdfalk
Copy link

gmdfalk commented Oct 20, 2016

Hi,

the docs lead me to believe that fluentd does not support Windows, see here:
http://docs.fluentd.org/articles/windows

If that is wrong, you might want to correct the documentation. If it's true, then i don't understand this pull request.
Would you mind clarifying exactly how i can use fluentd on Windows?

@tagomoris
Copy link
Member

That document is about Fluentd v0.12. Fluentd v0.14 (and master branch) supports Windows environment.
Documents about Fluentd v0.14 is under construction... there's not enough resource to do it :(

@repeatedly
Copy link
Member

I will add windows installation article on fluentd.org, not docs.fluentd.org.

@wolfgangihloff
Copy link

@repeatedly I do not see any details on documentation yet? All I find as of now is https://docs.fluentd.org/v0.12/articles/windows

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

Successfully merging this pull request may close these issues.