<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rant on falkp.no/blog</title>
    <link>/blog/tags/rant/</link>
    <description>falkp.no/blog (Rant)</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
      

      
    

    
    <lastBuildDate>Tue, 31 May 2016 00:00:00 +0000</lastBuildDate>
    
    <atom:link href="/blog/tags/rant/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Using finger service the wrong way</title>
      <link>/blog/posts/using_finger_service_the_wrong_way/</link>
      <pubDate>Tue, 31 May 2016 00:00:00 +0000</pubDate>
      
      <guid>/blog/posts/using_finger_service_the_wrong_way/</guid>
      <description>&lt;h2 id=&#34;overview&#34; &gt;
&lt;div&gt;
    &lt;a href=&#34;#overview&#34;&gt;
        #
    &lt;/a&gt;
    Overview
&lt;/div&gt;
&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;re doing this, you&amp;rsquo;re doing it wrong&amp;hellip;:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;2016-05-31 10:19:45.493314 Client 92.x.x.192 hamburg, germany/hamburg/hamburg
2016-05-31 10:19:48.443380 Client 74.x.x.189 greensboro, united_states/north_carolina/greensboro
2016-05-31 10:19:56.733260 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.745653 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.759656 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:19:56.819283 Client 50.x.x.50 beaverton, united_states/oregon/beaverton
2016-05-31 10:20:16.287744 Client 5.x.x.13 kaiserslautern, germany/rhineland-palatinate/kaiserslautern
2016-05-31 10:20:35.182942 Client 85.x.x.140 katowice, poland/silesia/katowice
2016-05-31 10:20:47.029550 Client 193.x.x.226 oslo, norway/oslo/oslo/oslo
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Lots of people use the finger service &lt;strong&gt;@graph.no&lt;/strong&gt; in an automated way. That&amp;rsquo;s quite alright, it&amp;rsquo;s what it&amp;rsquo;s there for. As an example:&lt;/p&gt;
&lt;p&gt;&lt;img src=&#34;sd_full.jpg&#34; alt=&#34;@graph.no used in an automated way at the Computer Science department at the KIT Karlsruhe&#34;&gt;&lt;/p&gt;
&lt;p&gt;But if you&amp;rsquo;re asking for the same data five times a second (until you get blocked by my firewall for a minute), you have to check your code. The data is at best changing every ~30 minutes.&lt;/p&gt;
&lt;p&gt;A likely scenario is putting it in &lt;strong&gt;screen&lt;/strong&gt;/&lt;strong&gt;tmux&lt;/strong&gt; status line. If you do that, you need to change how often your terminal multiplexer is updating the status line. A better way is to have a cron script fetching the data, and storing it in i.e. &lt;code&gt;/tmp/weather&lt;/code&gt; every 30-60 minutes, and then have your status line read from that.&lt;/p&gt;
&lt;p&gt;Another scenario could be people running it in &lt;strong&gt;watch&lt;/strong&gt;, which by default updates every two seconds. Also wrong. Please use -n 600 more.&lt;/p&gt;
&lt;p&gt;If you fetch the data, and &lt;strong&gt;grep&lt;/strong&gt; out what you need, then fetch the data once, and &lt;strong&gt;grep&lt;/strong&gt; all you like. Don&amp;rsquo;t fetch for each &lt;strong&gt;grep&lt;/strong&gt;. An example of this can be seen in the client &lt;a href=&#34;https://github.com/ways/pyyrascii/blob/master/graph.sh&#34;&gt;graph.sh&lt;/a&gt;, which fetches the data, &lt;strong&gt;sed&lt;/strong&gt; a lot and present it using unicode weather symbols and colors.&lt;/p&gt;
&lt;p&gt;Feel free to contact me if you need scripts/examples or have questions.&lt;/p&gt;
&lt;p&gt;Also, don&amp;rsquo;t feel ashamed, beaverton, you&amp;rsquo;re not alone in hammering me. I just don&amp;rsquo;t have any way to contact users. I still love you all. =)&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
