<?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: Grep-ing in Powershell</title>
	<atom:link href="http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm</link>
	<description>Not your everyday tech journal</description>
	<lastBuildDate>Tue, 03 Jan 2012 15:21:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: grep</title>
		<link>http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm/comment-page-1#comment-6274</link>
		<dc:creator>grep</dc:creator>
		<pubDate>Fri, 23 Dec 2011 17:22:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebits.info/?p=87#comment-6274</guid>
		<description>grep reads the content of the file, anything close to that in powershell would be get-content. So if you were looking for the string &quot;Successfully Completed&quot; in the .log files of a directory, here&#039;s what you could do:

Get-Content *.log &#124; where {$_ -match &quot;Successfully Completed&quot;}</description>
		<content:encoded><![CDATA[<p>grep reads the content of the file, anything close to that in powershell would be get-content. So if you were looking for the string &#8220;Successfully Completed&#8221; in the .log files of a directory, here&#8217;s what you could do:</p>
<p>Get-Content *.log | where {$_ -match &#8220;Successfully Completed&#8221;}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lord TCT</title>
		<link>http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm/comment-page-1#comment-6008</link>
		<dc:creator>Lord TCT</dc:creator>
		<pubDate>Mon, 25 Oct 2010 15:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebits.info/?p=87#comment-6008</guid>
		<description>Thanks for the tip Nelson!</description>
		<content:encoded><![CDATA[<p>Thanks for the tip Nelson!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Nelson</title>
		<link>http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm/comment-page-1#comment-5972</link>
		<dc:creator>Steve Nelson</dc:creator>
		<pubDate>Wed, 29 Sep 2010 16:29:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebits.info/?p=87#comment-5972</guid>
		<description>One caveat to this post...if you want to grep on a particular field other than the last one in the list, you have to explicitly specify the object.  Using the example above, to grep on the file length equaling 2888, you would have to use:

ls &#124; where {$_.Length -match 2888}</description>
		<content:encoded><![CDATA[<p>One caveat to this post&#8230;if you want to grep on a particular field other than the last one in the list, you have to explicitly specify the object.  Using the example above, to grep on the file length equaling 2888, you would have to use:</p>
<p>ls | where {$_.Length -match 2888}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry Loyd</title>
		<link>http://www.thebits.info/powershell/grep-ing-in-powershell-87.htm/comment-page-1#comment-5868</link>
		<dc:creator>Jerry Loyd</dc:creator>
		<pubDate>Tue, 29 Jun 2010 15:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.thebits.info/?p=87#comment-5868</guid>
		<description>Thanks for this post.  I was on the wrong track till I found this.  I just happen to be wanting to filter the Process list too!</description>
		<content:encoded><![CDATA[<p>Thanks for this post.  I was on the wrong track till I found this.  I just happen to be wanting to filter the Process list too!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

