<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Big Bad Code &#187; command line</title>
	<atom:link href="http://bigbadcode.com/category/command-line/feed/" rel="self" type="application/rss+xml" />
	<link>http://bigbadcode.com</link>
	<description>this blog is retired. I&#039;m leaving it up as a reference</description>
	<lastBuildDate>Wed, 19 Aug 2009 21:49:43 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Just sitting here watching the logs go by.</title>
		<link>http://bigbadcode.com/2008/12/22/just-sitting-here-watching-the-logs-go-by/</link>
		<comments>http://bigbadcode.com/2008/12/22/just-sitting-here-watching-the-logs-go-by/#comments</comments>
		<pubDate>Tue, 23 Dec 2008 00:12:01 +0000</pubDate>
		<dc:creator>jbloom</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Technical]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[snippet]]></category>

		<guid isPermaLink="false">http://bigbadcode.com/?p=207</guid>
		<description><![CDATA[Some times while working on remote servers I need to watch various log files. Typically for something like this I&#8217;ll create an extremely simple script that watches all the logs at once, since the next time I&#8217;m on that machine I&#8217;ll probably have forgotten the paths in question. Something like this: tail -f /var/www/apache/access.log /var/www/apache/error.log [...]]]></description>
			<content:encoded><![CDATA[<p>Some times while working on remote servers I need to watch various log files. Typically for something like this I&#8217;ll create an extremely simple script that watches all the logs at once, since the next time I&#8217;m on that machine I&#8217;ll probably have forgotten the paths in question.</p>
<p>Something like this:</p>
<pre>tail -f /var/www/apache/access.log /var/www/apache/error.log</pre>
<p>The problem with that approach is really long lines wrap and I usually just care about the far left of the file, so I&#8217;ve been looking for a way to turn off wrapping in tail. Unfortunately that seems to be impossible. I tried messing with my shell to kill the extra characters with this:</p>
<pre>echo -e "\e[?7l\c"</pre>
<p>But that was messing up other things. The best solution I&#8217;ve found so far is to use less with these options</p>
<pre>less +F -S /var/log/apache/access.log</pre>
<p>+F puts it in a tail like mode and -S chops the line to the screen width, the only drawback is that it doesn&#8217;t intersperse the 2 files like tail does. I was hoping to pipe tails input into less in the this fashion but that didn&#8217;t seem to work right either.</p>
]]></content:encoded>
			<wfw:commentRss>http://bigbadcode.com/2008/12/22/just-sitting-here-watching-the-logs-go-by/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Developing AIR Applications (and killing them when they misbehave)</title>
		<link>http://bigbadcode.com/2007/09/27/developing-air-applications-and-killing-them-when-they-misbehave/</link>
		<comments>http://bigbadcode.com/2007/09/27/developing-air-applications-and-killing-them-when-they-misbehave/#comments</comments>
		<pubDate>Thu, 27 Sep 2007 19:26:23 +0000</pubDate>
		<dc:creator>jbloom</dc:creator>
				<category><![CDATA[AIR]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[osx]]></category>

		<guid isPermaLink="false">http://bigbadcode.com/2007/09/27/developing-air-applications-and-killing-them-when-they-misbehave/</guid>
		<description><![CDATA[When developing AIR applications under flexbuilder you may get a situation where the app is stuck in an unresponsive state and refuses to quit itself. To kill it quickly on a Mac you can do the following from a terminal: ps -A &#124; grep adl That will return a line that looks something like this [...]]]></description>
			<content:encoded><![CDATA[<p>When developing AIR applications under flexbuilder you may get a situation where the app is stuck in an unresponsive state and refuses to quit itself. </p>
<p>To kill it quickly on a Mac you can do the following from a terminal:<br />
<code><br />
ps -A | grep adl<br />
</code></p>
<p>That will return a line that looks something like this<br />
<code><br />
18132  ??  S      0:22.97 /Users/joshbloom/Applications/flexb_183522/Adobe Flex Builder 3/sdks/3.0.0/bin/adl -runtime /Users/joshbloom/Appl<br />
18148  p1  S+     0:00.00 grep adl</code></p>
<p>The number at the beginning of the first line first line indicates the process ID of your unresponsive AIR app. </p>
<p>To kill it you would run this command:<br />
<code><br />
kill -9 18132<br />
</code></p>
<p>Be careful what number you put into the kill command, it will happily kill anything you tell it to. If you make a mistake you may have killed your window manager, your instant messenger or even something important like your twitter client. </p>
]]></content:encoded>
			<wfw:commentRss>http://bigbadcode.com/2007/09/27/developing-air-applications-and-killing-them-when-they-misbehave/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

