<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: 10 Awesome Examples for Viewing Huge Log Files in Unix</title>
	<atom:link href="http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/</link>
	<description>Guides, HowTos and Tips for Technology Geeks</description>
	<lastBuildDate>Thu, 09 Feb 2012 13:04:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: ks</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-90298</link>
		<dc:creator>ks</dc:creator>
		<pubDate>Wed, 02 Mar 2011 23:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-90298</guid>
		<description>A nice and handy tutorial. A few comments about the above comment by @logan:

$ cat logfile &#124; less
has the same effect as
$ less logfile
and  hence the  use of the pipe is redundant (&#039;$&#039; stands for the command prompt). Both lets you scroll through the logfile and search for pattern using &#039;/&#039; and &#039;?&#039; (similar to vim).

However, the second 
$ cat logfile &#124; less &#124; grep “PATTERN” 
does not let you scroll, but the following
$ grep &quot;PATTERN&quot; logfile &#124; less
will --- through only the the lines that has the matching pattern &quot;PATTERN&quot;.</description>
		<content:encoded><![CDATA[<p>A nice and handy tutorial. A few comments about the above comment by @logan:</p>
<p>$ cat logfile | less<br />
has the same effect as<br />
$ less logfile<br />
and  hence the  use of the pipe is redundant (&#8216;$&#8217; stands for the command prompt). Both lets you scroll through the logfile and search for pattern using &#8216;/&#8217; and &#8216;?&#8217; (similar to vim).</p>
<p>However, the second<br />
$ cat logfile | less | grep “PATTERN”<br />
does not let you scroll, but the following<br />
$ grep &#8220;PATTERN&#8221; logfile | less<br />
will &#8212; through only the the lines that has the matching pattern &#8220;PATTERN&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: logan</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-87793</link>
		<dc:creator>logan</dc:creator>
		<pubDate>Mon, 21 Feb 2011 06:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-87793</guid>
		<description>or you can always use

cat logfile &#124; less

which lets you scroll through it

OR 

cat logfile &#124; less &#124; grep &quot;PATTERN&quot; 

which lets you scroll through matching entries
I search for sshd for my auth.log file and can see all and only the ssh server entries</description>
		<content:encoded><![CDATA[<p>or you can always use</p>
<p>cat logfile | less</p>
<p>which lets you scroll through it</p>
<p>OR </p>
<p>cat logfile | less | grep &#8220;PATTERN&#8221; </p>
<p>which lets you scroll through matching entries<br />
I search for sshd for my auth.log file and can see all and only the ssh server entries</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anton</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-57796</link>
		<dc:creator>anton</dc:creator>
		<pubDate>Fri, 06 Aug 2010 09:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-57796</guid>
		<description>Is the following any better (i.e. more efficient) than zcat logfile.gz &#124; tail ???

# emulate ztail ???

zless +F logfile.gz</description>
		<content:encoded><![CDATA[<p>Is the following any better (i.e. more efficient) than zcat logfile.gz | tail ???</p>
<p># emulate ztail ???</p>
<p>zless +F logfile.gz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-53948</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Wed, 14 Jul 2010 14:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-53948</guid>
		<description>You showed zcat, but there is also bzcat and lzcat, and probably a few others. so if you have a file that is bzip2&#039;d or lzma&#039;d, then you can use bzcat and lzcat respectively to display them. Also, it can be piped to the less command so it can be scrolled across the terminal.</description>
		<content:encoded><![CDATA[<p>You showed zcat, but there is also bzcat and lzcat, and probably a few others. so if you have a file that is bzip2&#8242;d or lzma&#8217;d, then you can use bzcat and lzcat respectively to display them. Also, it can be piped to the less command so it can be scrolled across the terminal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HowTo: The Ultimate Logrotate Command Tutorial with 10 Examples</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-53891</link>
		<dc:creator>HowTo: The Ultimate Logrotate Command Tutorial with 10 Examples</dc:creator>
		<pubDate>Wed, 14 Jul 2010 06:03:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-53891</guid>
		<description>[...] Also, if you are having huge log files, you can use: 10 Awesome Examples for Viewing Huge Log Files in Unix [...]</description>
		<content:encoded><![CDATA[<p>[...] Also, if you are having huge log files, you can use: 10 Awesome Examples for Viewing Huge Log Files in Unix [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bipin</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-46024</link>
		<dc:creator>Bipin</dc:creator>
		<pubDate>Thu, 06 May 2010 11:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-46024</guid>
		<description>Great stuffs. Thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Great stuffs. Thanks for sharing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-17305</link>
		<dc:creator>Ted</dc:creator>
		<pubDate>Sun, 13 Sep 2009 06:06:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-17305</guid>
		<description>The sed tip I will use for sure and I also like the tail -f &#124;grep.  Thank you Ramesh. 

Any chance you will be posting your most useful sed commands from your note book at some time?</description>
		<content:encoded><![CDATA[<p>The sed tip I will use for sure and I also like the tail -f |grep.  Thank you Ramesh. </p>
<p>Any chance you will be posting your most useful sed commands from your note book at some time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 3 Methods To View tail -f output of Multiple Log Files in One Terminal</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-17124</link>
		<dc:creator>3 Methods To View tail -f output of Multiple Log Files in One Terminal</dc:creator>
		<pubDate>Wed, 09 Sep 2009 06:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-17124</guid>
		<description>[...] Typically you may open multiple terminals to view tail -f of multiple files as we explained in our previous 10 examples to view unix log files. [...]</description>
		<content:encoded><![CDATA[<p>[...] Typically you may open multiple terminals to view tail -f of multiple files as we explained in our previous 10 examples to view unix log files. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ShekarKCB</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-15691</link>
		<dc:creator>ShekarKCB</dc:creator>
		<pubDate>Mon, 24 Aug 2009 11:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-15691</guid>
		<description>Nice Article,  uses of head, tail, and sed were nicely covered. Thanks for the same.</description>
		<content:encoded><![CDATA[<p>Nice Article,  uses of head, tail, and sed were nicely covered. Thanks for the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramesh Natarajan</title>
		<link>http://www.thegeekstuff.com/2009/08/10-awesome-examples-for-viewing-huge-log-files-in-unix/comment-page-1/#comment-14525</link>
		<dc:creator>Ramesh Natarajan</dc:creator>
		<pubDate>Fri, 14 Aug 2009 14:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.thegeekstuff.com/?p=1136#comment-14525</guid>
		<description>@Robert,

Sed can do lot of amazing things. But it is hard to remember those on top of your head. I have close to 100 sed command that solves some common problem in a notebook, which I copy/paste whenever nedded.

Example 1 of this article is in that list. :)

@Nico,

Thanks for pointing that out. Most of us forget that grep can be combined with &quot;tail -f&quot;. This indeed can be very handy.

@Nicholas,

Don&#039;t worry. I&#039;ve done similar mistakes several times. So, I can related to it. :-)

@Ashish, @Koen

I&#039;m very glad that you found this article helpful.

@Ronald,

Yeah. That is the beauty of Unix. We can do amazing things with linux commands that were not even clearly mentioned in the manual. This is also the reason Windows admins don&#039;t like Linux, as they hate reading manuals. Even when they read the manuals, it is not really explained very well.</description>
		<content:encoded><![CDATA[<p>@Robert,</p>
<p>Sed can do lot of amazing things. But it is hard to remember those on top of your head. I have close to 100 sed command that solves some common problem in a notebook, which I copy/paste whenever nedded.</p>
<p>Example 1 of this article is in that list. <img src='http://www.thegeekstuff.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@Nico,</p>
<p>Thanks for pointing that out. Most of us forget that grep can be combined with &#8220;tail -f&#8221;. This indeed can be very handy.</p>
<p>@Nicholas,</p>
<p>Don&#8217;t worry. I&#8217;ve done similar mistakes several times. So, I can related to it. <img src='http://www.thegeekstuff.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>@Ashish, @Koen</p>
<p>I&#8217;m very glad that you found this article helpful.</p>
<p>@Ronald,</p>
<p>Yeah. That is the beauty of Unix. We can do amazing things with linux commands that were not even clearly mentioned in the manual. This is also the reason Windows admins don&#8217;t like Linux, as they hate reading manuals. Even when they read the manuals, it is not really explained very well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced
Content Delivery Network via Amazon Web Services: CloudFront: static.thegeekstuff.com

Served from: www.thegeekstuff.com @ 2012-02-09 13:39:08 -->
