-
Notifications
You must be signed in to change notification settings - Fork 897
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
Option to make stdout unbuffered #211
Comments
mstemm
changed the title
Option to make stdout buffered
Option to make stdout unbuffered
Feb 26, 2017
mstemm
added a commit
that referenced
this issue
Oct 6, 2017
Add the ability to keep file/program outputs open (i.e. writing to the same open file/program for multiple notifications). A new option to the file/program output "keep_alive", if true, keeps the file/program pipe open across events. This makes the need for unbuffered output aka #211 more pressing. Will add that next.
mstemm
added a commit
that referenced
this issue
Oct 6, 2017
Add the ability to keep file/program outputs open (i.e. writing to the same open file/program for multiple notifications). A new option to the file/program output "keep_alive", if true, keeps the file/program pipe open across events. This makes the need for unbuffered output aka #211 more pressing. Will add that next.
mstemm
added a commit
that referenced
this issue
Oct 6, 2017
Add the ability to keep file/program outputs open (i.e. writing to the same open file/program for multiple notifications). A new option to the file/program output "keep_alive", if true, keeps the file/program pipe open across events. This makes the need for unbuffered output aka #211 more pressing. Will add that next.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add an option to make standard output unbuffered. Sysdig has an --unbuffered option so we should use that name for consistency.
The text was updated successfully, but these errors were encountered: