Pete Heist &lt;notifications@github.com&gt; writes:<br>
<br>
&gt;&gt; Could you be persuaded to add a &#39;check_server&#39; action to irtt? Something<br>
&gt;&gt; that just does the handshake and doesn&#39;t run any more tests other than<br>
&gt;&gt; that. Then we could have Flent call that to verify that irtt is<br>
&gt;&gt; usable...<br>
&gt;<br>
&gt; Sure, I’ll add that (or something similarly named). Should get to it<br>
&gt; today or tomorrow. Meanwhile you’re right that something like this<br>
&gt; works and check for return code 0 to mean success:<br>
<br>
Cool!<br>
<br>
&gt; The handshake takes up to 15 seconds to complete (delays of 1, 2, 4<br>
&gt; and 8 seconds waiting for a reply), so not having irtt on the server<br>
&gt; will mean a 15 second wait. Do you think it’s ok to keep that fixed?<br>
<br>
Hmm, waiting 15 seconds before starting a test is probably a bit much.<br>
For the test, I&#39;d say don&#39;t retransmit and make the wait configurable?<br>
<br>
-Toke<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/tohojo/flent/issues/106#issuecomment-344912942">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AerUv-JFQyQ2MGXe1pVBH1YDqg3NSXsUks5s3C8kgaJpZM4MpJAm">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AerUvxogJMafv0ifdgPGBElHmVVJluGZks5s3C8kgaJpZM4MpJAm.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/tohojo/flent/issues/106#issuecomment-344912942"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/tohojo/flent","title":"tohojo/flent","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/tohojo/flent"}},"updates":{"snippets":[{"icon":"PERSON","message":"@tohojo in #106: Pete Heist \u003cnotifications@github.com\u003e writes:\n\n\u003e\u003e Could you be persuaded to add a 'check_server' action to irtt? Something\n\u003e\u003e that just does the handshake and doesn't run any more tests other than\n\u003e\u003e that. Then we could have Flent call that to verify that irtt is\n\u003e\u003e usable...\n\u003e\n\u003e Sure, I’ll add that (or something similarly named). Should get to it\n\u003e today or tomorrow. Meanwhile you’re right that something like this\n\u003e works and check for return code 0 to mean success:\n\nCool!\n\n\u003e The handshake takes up to 15 seconds to complete (delays of 1, 2, 4\n\u003e and 8 seconds waiting for a reply), so not having irtt on the server\n\u003e will mean a 15 second wait. Do you think it’s ok to keep that fixed?\n\nHmm, waiting 15 seconds before starting a test is probably a bit much.\nFor the test, I'd say don't retransmit and make the wait configurable?\n\n-Toke\n"}],"action":{"name":"View Issue","url":"https://github.com/tohojo/flent/issues/106#issuecomment-344912942"}}}</script>