-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feedback on Open-stream stats #123
Comments
Try specifying interrupt type, eg. If you plan to invoke from inside a bash script, you can try something like this.
|
It does seem SIGTERM may not be triggering the cleanup sequence in code (which triggers |
Could I make another suggestion please: the line of output per packet will be too much for us, though the "Pass summary" may be useful. Could there be a --summary option which does just the summary? |
i think "real time stats" outputs every 2 second at current setting (not configurable). it is triggered by a timer and not by packet. |
Ah yes, it is. Ok - I can live with that then :) |
sorry i just realized, currently
i realize this may be a confusing design, maybe we should just make it user configurable, and separating the pass summary might be a good idea. |
Can you confirm if this the behaviour on 0.8.1 please? With stats+verbose I see just the pass summary at the end; with stats+debug (with or without verbose) I additionally get the real time stats, but on every packet. |
I realise this is still an Alpha feature but I thought I'd point out that, although the open-stream stats are dumped if the user hits Ctrl-C, they aren't if the process is terminated by e.g. Linux 'timeout' command.
The text was updated successfully, but these errors were encountered: