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

Access 'live' console output #113

Closed
t-knapp opened this issue May 1, 2016 · 2 comments
Closed

Access 'live' console output #113

t-knapp opened this issue May 1, 2016 · 2 comments

Comments

@t-knapp
Copy link

t-knapp commented May 1, 2016

I am trying to access the output of tinc join INVITATION and tinc -n NETWORK start -D -d3 via an AutoIT Script on Windows 7.

I neither can read 'live' output generated by tinc join nor tinc start. But reading tinc --version or tinc --help works.

I also tried to access the console output via Java, but the output is always empty, while tinc is running.

Do you use different techniques to write to console in tinc --version and tinc start?

@gsliepen
Copy link
Owner

gsliepen commented May 1, 2016

On Sun, May 01, 2016 at 07:17:44AM -0700, Tobias Knapp wrote:

I am trying to access the output of tinc join INVITATION and tinc -n NETWORK start -D -d3 via an AutoIT Script on Windows 7.

I neither can read 'live' output generated by tinc join nor tinc start. But reading tinc --version or tinc --help works.

I also tried to access the console output via Java, but the output is always empty, while tinc is running.

Do you use different techniques to write to console in tinc --version and tinc start?

Note that there are two outputs; stdout and stderr. You should handle
both in your AutoIT Script. Tinc mostly writes to stderr, unless asked
specifically for some output (like --version, or the "tinc get" or "tinc
invite" commands).

Met vriendelijke groet / with kind regards,
Guus Sliepen guus@tinc-vpn.org

@t-knapp
Copy link
Author

t-knapp commented May 1, 2016

Thank you. Reading stderr works.

@t-knapp t-knapp closed this as completed May 1, 2016
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