<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>ISA 2000: Filter Proxy Logs with FIND</title><link>http://blogs.technet.com/tristank/archive/2004/07/13/181555.aspx</link><description>I'm often faced with the somewhat daunting task of wading through a 500MB log file to try to identify a problem with one user of a proxy server. I find the simplest way to even the odds a bit - using out-of-the-box tools - is to use the humble FIND command</description><dc:language>en-AU</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: ISA 2000: Filter Proxy Logs with FIND</title><link>http://blogs.technet.com/tristank/archive/2004/07/13/181555.aspx#181621</link><pubDate>Wed, 14 Jul 2004 04:57:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:181621</guid><dc:creator>Jodee R.</dc:creator><description>You could also use qgrep from the Resource Kit and that gives you about 14 options (regular expressions!) compared to find's 4.</description></item><item><title>ISA 2004: New-Style Log Filtering and Export</title><link>http://blogs.technet.com/tristank/archive/2004/07/13/181555.aspx#213985</link><pubDate>Fri, 13 Aug 2004 10:16:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:213985</guid><dc:creator>Extra Bits That Didn't Fit</dc:creator><description /></item></channel></rss>