<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with searchutility]]></title><description><![CDATA[A list of topics that have been tagged with searchutility]]></description><link>https://board.circlewithadot.net/tags/searchutility</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 07:41:16 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/tags/searchutility.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[This started out as a personal project.]]></title><description><![CDATA[This started out as a personal project.  Mainly because when working with vendor support, they wanted logs and logs and logs. Finally figured out w/ a few vendors what they were looking for. But when a directory contains over 100 log files and directories, where do you begin searching?I recently, re-wrote the entire program, yes with a little bit of AI help, to fix issues I was facing and add more functionality. Being able to navigate a directory of hundreds of logs to just a few to speed up your troubleshooting time helps keep you slightly sane. https://github.com/rrice2004/Python-/tree/main/LogFile%20Search#python #logfiles #searchutility]]></description><link>https://board.circlewithadot.net/topic/40286b79-48c7-457f-94f9-9e1ed618dcab/this-started-out-as-a-personal-project.</link><guid isPermaLink="true">https://board.circlewithadot.net/topic/40286b79-48c7-457f-94f9-9e1ed618dcab/this-started-out-as-a-personal-project.</guid><dc:creator><![CDATA[fringedcrow@infosec.exchange]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>