-
Notifications
You must be signed in to change notification settings - Fork 77
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
ss: command not found
on macOS
#177
Comments
Hi Rich,
the unfortunately named socket stats binary ss, is as far as I can tell Linux only, so simply not present in the BSDs and their offspring.
Best Regards
Sebastian
… On Sep 5, 2019, at 14:48, Rich Brown ***@***.***> wrote:
Spurred on by Dave's Coffee Shop Bloat Test script, I decided to try it on my Mac (10.12.6) with Flent 1.3.0. This command seemed to work fine:
flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 tcp_ndown
But I got a ton of error messages when I tried the second command using the --socket-stats option: there were none if I left that off. What other information could I provide? Thanks.
bash-3.2$ flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 --socket-stats tcp_nup
Started Flent 1.3.0 using Python 2.7.15.
Starting tcp_nup test. Expected run time: 70 seconds.
WARNING: Command produced no valid data.
Runner class: SsRunner
Command: /bin/bash /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh -I 0.20 -c 300 -H localhost -t
'23.239.20.41' -f ' and dport != 12865'
Return code: 0
Stdout: Time: 1567685642.N
---
Time: 1567685642.N
---
Time: 1567685642.N
... a zillion of these lines, followed by ...
Time: 1567685705.N
---
Time: 1567685706.N
---
Time: 1567685706.N
---
Stderr: /usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss:
command
not found
/usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss:
command
not found
... a zillion of these lines, and finally ...
/usr/local/lib/python2.7/site-packages/flent/scripts/ss_iterate.sh: line 55: ss:
command
not found
Data file written to ./tcp_nup-2019-09-05T081356.815453.Rich_Test.flent.gz.
Summary of tcp_nup
test
run from 2019-09-05 12:13:56.815453
Title:
'Rich_Test'
avg median
# data pts
Ping (ms) ICMP
:
100.69 101.00 ms 349
TCP upload avg
:
0.18 0.18 Mbits/s 101
TCP upload sum
:
0.31 0.30 Mbits/s 101
TCP upload::1
:
0.15 0.13 Mbits/s 7
TCP upload::2
:
0.23 0.21 Mbits/s 11
TCP upload::3
:
0.17 0.17 Mbits/s 8
TCP upload::4
:
0.23 0.21 Mbits/s 11
bash-3.2$
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
_______________________________________________
Flent-users mailing list
***@***.***
http://flent.org/mailman/listinfo/flent-users_flent.org
|
Rich Brown <notifications@github.com> writes:
Spurred on by Dave's [Coffee Shop Bloat Test](https://lists.bufferbloat.net/pipermail/bloat/2019-September/009336.html) script, I decided to try it on my Mac (10.12.6) with Flent 1.3.0. This command seemed to work fine:
`flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 tcp_ndown`
But I got a ton of error messages when I tried the second command
using the `--socket-stats` option: there were none if I left that off.
What other information could I provide? Thanks.
Hmm, not sure there's anything to be done about that; as it says, that
command doesn't exist on OSX. So, erm, just leave out the --socket-stats
option? :)
…-Toke
|
Good advice. Done. |
Well, I'd LOVE it if we suppotedOSX for thuis |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spurred on by Dave's Coffee Shop Bloat Test script, I decided to try it on my Mac (10.12.6) with Flent 1.3.0. This command seemed to work fine:
flent -x -H flent-fremont.bufferbloat.net -t Rich_Test --te=upload_streams=4 tcp_ndown
But I got a ton of error messages when I tried the second command using the
--socket-stats
option: there were none if I left that off. What other information could I provide? Thanks.The text was updated successfully, but these errors were encountered: