<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>mark</title>
	<atom:link href="http://blogs.splunk.com/mark/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.splunk.com/mark</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Wed, 21 May 2008 00:52:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Using splunk in Fedora9 x86_64</title>
		<link>http://blogs.splunk.com/mark/2008/05/20/using-splunk-in-fedora9-x86_64/</link>
		<comments>http://blogs.splunk.com/mark/2008/05/20/using-splunk-in-fedora9-x86_64/#comments</comments>
		<pubDate>Wed, 21 May 2008 00:52:37 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[dev]]></category>

		<category><![CDATA[hacks]]></category>

		<category><![CDATA[Flash]]></category>

		<category><![CDATA[Linux]]></category>

		<category><![CDATA[x86_64]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2008/05/20/using-splunk-in-fedora9-x86_64/</guid>
		<description><![CDATA[For those who use Linux as their primary desktop, using splunk can be a chore. Splunk dashboards are built on Flash9. So, you will likely need the following commands (as root, or sudo) to get Flash working.

rpm -ivh http://fpdownload.macromedia.com/get/flashplayer/current/flash-plugin-9.0.124.0-release.i386.rpm
yum install nspluginwrapper.{i386,x86_64} pulseaudio-lib.i386
yum install flash-plugin
yum erase rhythmbox.*
mozilla-plugin-config -i -g -v
mozilla-plugin-config nspluginwrapper -i /usr/lib/mozilla/plugins/libflashplayer.so

(Optionally, if you haven&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p>For those who use Linux as their primary desktop, using splunk can be a chore. Splunk dashboards are built on Flash9. So, you will likely need the following commands (as root, or sudo) to get Flash working.</p>
<ul>
<li>rpm -ivh http://fpdownload.macromedia.com/get/flashplayer/current/flash-plugin-9.0.124.0-release.i386.rpm</li>
<li>yum install nspluginwrapper.{i386,x86_64} pulseaudio-lib.i386</li>
<li>yum install flash-plugin</li>
<li>yum erase rhythmbox.*</li>
<li>mozilla-plugin-config -i -g -v</li>
<li>mozilla-plugin-config nspluginwrapper -i /usr/lib/mozilla/plugins/libflashplayer.so</li>
</ul>
<p>(Optionally, if you haven&#8217;t imported the Adobe GPG key, you will have to run the following command)</p>
<ul>
<li>#rpm &#8211;import /etc/pki/rpm-gpg/RPM-GPG-KEY-adobe-linux</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2008/05/20/using-splunk-in-fedora9-x86_64/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Splunk2LCD : Display your Alerts on an LCD</title>
		<link>http://blogs.splunk.com/mark/2008/02/22/splunk2lcd-display-your-alerts-on-an-lcd/</link>
		<comments>http://blogs.splunk.com/mark/2008/02/22/splunk2lcd-display-your-alerts-on-an-lcd/#comments</comments>
		<pubDate>Sat, 23 Feb 2008 01:08:18 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[hacks]]></category>

		<category><![CDATA[tech]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2008/02/22/splunk2lcd-display-your-alerts-on-an-lcd/</guid>
		<description><![CDATA[This morning I got a nice little LCD from <a href="http://www.crystalfontz.com" target="_blank">Crystalfontz</a> that allows me to connect to it via the open source project <a href="http://www.lcdproc.org" target="_blank">lcdproc</a>.  After a bit of compiling and installing, LCDproc (which runs natively on linux, darwin (osx) and most other unix distros) connects to any serial, parallel or USB LCD device. In this case, the Crystalfontz LCD is  4 line by 20 character display.

<a href="http://dev.splunk.com/wp-content/uploads/2008/02/p1000621.JPG" title="Splunk2LCD"><img src="http://dev.splunk.com/wp-content/uploads/2008/02/p1000621.JPG" alt="Splunk2LCD" /></a>

Once configured and connected, you start the server and accept connections.

I then grabbed the IO-LCDproc perl module and modified it to display to the LCDproc server. You can get the IO-LCDproc through CPAN.
]]></description>
			<content:encoded><![CDATA[<p>This morning I got a nice little LCD from <a href="http://www.crystalfontz.com" target="_blank">Crystalfontz</a> that allows me to connect to it via the open source project <a href="http://www.lcdproc.org" target="_blank">lcdproc</a>.  After a bit of compiling and installing, LCDproc (which runs natively on linux, darwin (osx) and most other unix distros) connects to any serial, parallel or USB LCD device. In this case, the Crystalfontz LCD is  4 line by 20 character display.</p>
<p><a href="http://blogs.splunk.com/devuploads/2008/02/p1000621.JPG" title="Splunk2LCD"><img src="http://blogs.splunk.com/devuploads/2008/02/p1000621.JPG" alt="Splunk2LCD" /></a></p>
<p>Once configured and connected, you start the server and accept connections.</p>
<p>I then grabbed the IO-LCDproc perl module and modified it to display to the LCDproc server. You can get the IO-LCDproc through CPAN.</p>
<p>Here is the code that would go in your $SPLUNK_HOME/bin/scripts directory</p>
<p>[source:python]<br />
#!/use/bin/perl -w<br />
use IO::LCDproc;<br />
use IO::Socket;<br />
use strict;</p>
<p>&amp;usage if (! $ARGV[0]);</p>
<p>my $client = IO::LCDproc::Client-&gt;new(host =&gt; &#8220;localhost&#8221;, name =&gt; &#8220;MYNAME&#8221;, port =&gt; &#8220;13666&#8243;);</p>
<p>my $screen = IO::LCDproc::Screen-&gt;new(name =&gt; &#8220;screen&#8221;);</p>
<p>my $title = IO::LCDproc::Widget-&gt;new( name =&gt; &#8220;date&#8221;, type =&gt; &#8220;title&#8221;);</p>
<p>my $first = IO::LCDproc::Widget-&gt;new(<br />
name =&gt; &#8220;first&#8221;, align =&gt; &#8220;center&#8221;, type =&gt; &#8220;string&#8221;, xPos =&gt; 1, yPos =&gt; 2,<br />
data =&gt; &#8220;test&#8221;);<br />
my $second = IO::LCDproc::Widget-&gt;new(<br />
name =&gt; &#8220;second&#8221;, align =&gt; &#8220;center&#8221;, type =&gt; &#8220;string&#8221;, xPos =&gt; 1, yPos =&gt; 3<br />
);<br />
my $third = IO::LCDproc::Widget-&gt;new(<br />
name =&gt; &#8220;third&#8221;, align =&gt; &#8220;center&#8221;, type =&gt; &#8220;string&#8221;, xPos =&gt; 1, yPos =&gt; 4<br />
);</p>
<p>$client-&gt;add ( $screen );<br />
$screen-&gt;add ( $title, $first, $second, $third );<br />
$client-&gt;connect() or die &#8220;Cannot Connect: $!&#8221;;<br />
$client-&gt;initialize();</p>
<p>$title-&gt;set( data =&gt; &#8220;Splunk2LCD&#8221; );<br />
$first-&gt;set( data =&gt; &#8220;$ARGV[1]&#8221; );<br />
$second-&gt;set( data =&gt; &#8220;$ARGV[4]&#8221; );<br />
$third-&gt;set( data =&gt; &#8220;$ARGV[5]&#8221; );</p>
<p>sleep 5;<br />
exit 1;</p>
<p>sub usage {<br />
  print &lt;&lt;USAGE;<br />
  LCDproc Client for Splunk<br />
  Mark Cohen<br />
  Usage: ./splunk2lcd2.pl ARGV0 ARGV1 ARGV2<br />
  USAGE<br />
  exit 1;<br />
}<br />
[/source]</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2008/02/22/splunk2lcd-display-your-alerts-on-an-lcd/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Splunking your iPhone</title>
		<link>http://blogs.splunk.com/mark/2007/08/26/splunking-your-iphone/</link>
		<comments>http://blogs.splunk.com/mark/2007/08/26/splunking-your-iphone/#comments</comments>
		<pubDate>Sun, 26 Aug 2007 08:08:34 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[Homepage]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2007/08/26/splunking-your-iphone/</guid>
		<description><![CDATA[Had a little fun last night. Enabled syslogd on the iPhone and sent the logs to a splunk instance via UDP/514
Process is hacking your iPhone and install ssh. Enable syslogd by the following method. (Thanks to core on #iphone)
syslog
20:00  so to get syslog running you need /etc/syslogd.conf from your mac
20:01  then break the [...]]]></description>
			<content:encoded><![CDATA[<p>Had a little fun last night. Enabled syslogd on the iPhone and sent the logs to a splunk instance via UDP/514</p>
<p>Process is hacking your iPhone and install ssh. Enable syslogd by the following method. (Thanks to core on #iphone)</p>
<div align="left"><strong>syslog</strong></div>
<div align="left">20:00  so to get syslog running you need /etc/syslogd.conf from your mac</div>
<div align="left">20:01  then break the syslog in /System/Library/LaunchDaemons/apple.com.syslogd by putting in bad values</div>
<div align="left">20:01  then restart the phone and run 20:01  /usr/sbin/syslogd -bsd_out 1 &#38;</div>
<p>Then edit /etc/syslog.conf and append *.*            @loghost</p>
<p>Restart syslogd and you&#8217;re set.</p>
<p>Then just set splunk up to listen on 514/UDP and you have iPhone logs.</p>
<p>Interesting bit found? launchd, the service that starts up the daemons on the iPhone just keeps respawning services. The iPhone lacks a standard service control mechanism such as the sysv-compatible init process.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2007/08/26/splunking-your-iphone/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Rant on Syslogd</title>
		<link>http://blogs.splunk.com/mark/2007/04/25/rant-on-syslogd/</link>
		<comments>http://blogs.splunk.com/mark/2007/04/25/rant-on-syslogd/#comments</comments>
		<pubDate>Thu, 26 Apr 2007 00:46:44 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[Homepage]]></category>

		<category><![CDATA[rants]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2007/04/25/rant-on-syslogd/</guid>
		<description><![CDATA[Syslogd really should either be modified or ditched for syslog-ng. As anyone who looks at logs knows, its crucial to have full, standard time stamps. This should include, HH:MM:SS:MS YYYY-MM-DD.Rfc3164 states :


5.1 Dates and Time

It has been found that some network administrators like to archive
their syslog messages over long periods of time.  It has [...]]]></description>
			<content:encoded><![CDATA[<p>Syslogd really should either be modified or ditched for syslog-ng. As anyone who looks at logs knows, its crucial to have full, standard time stamps. This should include, HH:MM:SS:MS YYYY-MM-DD.Rfc3164 states :</p>
<pre>
<pre>
<h3><a name="section-5.1"></a>5.1 Dates and Time</h3>

It has been found that some network administrators like to archive
their syslog messages over long periods of time.  It has been seen
that some original syslog messages contain a more explicit time stamp
in which a 2 character or 4 character year field immediately follows
the space terminating the TIMESTAMP.  This is not consistent with the
original intent of the order and format of the fields.  If
implementers wish to contain a more specific date and time stamp
within the transmitted message, it should be within the CONTENT
field.  Implementers may wish to utilize the ISO 8601 [<a href="http://tools.ietf.org/html/rfc3164#ref-7">7</a>] date and
time formats if they want to include more explicit date and time
information.

Additional methods to address this desire for long-term archiving
have been proposed and some have been successfully implemented.  One
such method is that the network administrators may choose to modify
the messages stored on their collectors.  They may run a simple
script to add the year, and any other information, to each stored
record.  Alternatively, the script may replace the stored time with a
format more appropriate for the needs of the network administrators.
Another alternative has been to insert a record into the file that
contains the current year.  By association then, all other records
near that informative record should have been received in that same
year.  Neither of these however, addresses the issue of associating a
correct timezone with each record.</pre>
</pre>
<p>IMHO, this is backwards. We shouldn&#8217;t require developers to put the year in the content field or have people post process logs to include the year.. Syslog should properly write out the year.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2007/04/25/rant-on-syslogd/feed/</wfw:commentRss>
		</item>
		<item>
		<title>selinux and splunk</title>
		<link>http://blogs.splunk.com/mark/2006/11/21/selinux-and-splunk/</link>
		<comments>http://blogs.splunk.com/mark/2006/11/21/selinux-and-splunk/#comments</comments>
		<pubDate>Wed, 22 Nov 2006 03:40:55 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[Homepage]]></category>

		<category><![CDATA[hacks]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2006/11/21/selinux-and-splunk/</guid>
		<description><![CDATA[If you&#8217;ve enabled selinux for whatever reason, you need to either disable it or configure it to allow splunk to run.
To configure selinux to allow splunk to run, you need to run the chcon command on the splunk lib directory. Here is what you type :
chcon -c -v -R -u system_u -r object_r -t lib_t [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;ve enabled selinux for whatever reason, you need to either disable it or configure it to allow splunk to run.</p>
<p>To configure selinux to allow splunk to run, you need to run the chcon command on the splunk lib directory. Here is what you type :</p>
<p>chcon -c -v -R -u system_u -r object_r -t lib_t $SPLUNK_HOME/lib 2&gt;&#38;1 &gt; /dev/null<br />
You can also disable the check when splunk starts by adding this line to the $SPLUNK_HOME/bin/setSplunkEnv script</p>
<p>export SPLUNK_IGNORE_SELINUX=1</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2006/11/21/selinux-and-splunk/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Telling Splunk to not phone home for update info.</title>
		<link>http://blogs.splunk.com/mark/2006/11/21/telling-splunk-to-not-phone-home-for-update-info/</link>
		<comments>http://blogs.splunk.com/mark/2006/11/21/telling-splunk-to-not-phone-home-for-update-info/#comments</comments>
		<pubDate>Wed, 22 Nov 2006 03:22:21 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[Homepage]]></category>

		<category><![CDATA[hacks]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2006/11/21/telling-splunk-to-not-phone-home-for-update-info/</guid>
		<description><![CDATA[(2.1.1 only)
We&#8217;ve had a few people ask for this. Its going to be in the documentation eventually, but until then here is how you do it.
Edit $SPLUNK_HOME/etc/myinstall/search.xml
Change :
&#60;updateCheckerBaseURL&#62;http://quickdraw.splunk.com/js/&#60;/updateCheckerBaseURL&#62; &#60;updateCheckerBaseURL&#62;0&#60;/updateCheckerBaseURL&#62;
(2.1)
$SPLUNK_HOME/share/splunk/search/static/js/update_checker_pro.js.
At the top of the file, and within that same setup function, comment out these two lines:
createUpdateCheckerScriptlet();
setTimeout(&#8217;possiblyFallBackToCannotConnectMessage()&#8217;, 5000);
]]></description>
			<content:encoded><![CDATA[<p>(2.1.1 only)</p>
<p>We&#8217;ve had a few people ask for this. Its going to be in the documentation eventually, but until then here is how you do it.</p>
<p>Edit $SPLUNK_HOME/etc/myinstall/search.xml</p>
<p>Change :</p>
<p>&lt;updateCheckerBaseURL&gt;http://quickdraw.splunk.com/js/&lt;/updateCheckerBaseURL&gt; &lt;updateCheckerBaseURL&gt;0&lt;/updateCheckerBaseURL&gt;</p>
<p>(2.1)</p>
<p>$SPLUNK_HOME/share/splunk/search/static/js/update_checker_pro.js.</p>
<p>At the top of the file, and within that same setup function, comment out these two lines:<br />
createUpdateCheckerScriptlet();<br />
setTimeout(&#8217;possiblyFallBackToCannotConnectMessage()&#8217;, 5000);</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2006/11/21/telling-splunk-to-not-phone-home-for-update-info/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Allowing users to log in with HTTP GET in 2.1x</title>
		<link>http://blogs.splunk.com/mark/2006/10/09/allowing-users-to-log-in-with-http-get-in-21x/</link>
		<comments>http://blogs.splunk.com/mark/2006/10/09/allowing-users-to-log-in-with-http-get-in-21x/#comments</comments>
		<pubDate>Tue, 10 Oct 2006 04:41:31 +0000</pubDate>
		<dc:creator>mark</dc:creator>
		
		<category><![CDATA[Homepage]]></category>

		<category><![CDATA[hacks]]></category>

		<guid isPermaLink="false">http://blogs.splunk.com/mark/2006/10/09/allowing-users-to-log-in-with-http-get-in-21x/</guid>
		<description><![CDATA[I&#8217;ve had to field a few of these requests so here goes.
Assuming you understand that by doing this, you send users and passwords in clear text and the risks involved.
There is a way to do this through http GET, but it requires modifying a bit of python.
Edit line 395 of XMLResourse.py located in $SPLUNK_HOME/lib/python2.4/site-packages/splunk/search/XMLResource.py
def render_GET(self, [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve had to field a few of these requests so here goes.</p>
<p>Assuming you understand that by doing this, you send users and passwords in clear text and the risks involved.</p>
<p>There is a way to do this through http GET, but it requires modifying a bit of python.</p>
<p>Edit line 395 of XMLResourse.py located in $SPLUNK_HOME/lib/python2.4/site-packages/splunk/search/XMLResource.py</p>
<p>def render_GET(self, request) :<br />
# backdoor so scripts can auto-login just with a GET request instead of having to craft a proper HTTP POST.  Doesnt help said script keep track of the cookie, which is the hard part.<br />
#if (&#8221;usr&#8221; in request.args) and (&#8221;pwd&#8221; in request.args) :<br />
#    return self.render_POST(request)<br />
logger.debug(&#8221;LoginResource.render_GET&#8221;)<br />
sessNS = request.getSession().sessionNamespaces</p>
<p>Uncomment out the if and return lines and restart splunk.</p>
<p>To log in, you would enter this URL</p>
<p>http://your.host/login?usr=username&#38;pwd=password</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.splunk.com/mark/2006/10/09/allowing-users-to-log-in-with-http-get-in-21x/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
