<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: find a string in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874861#M99343</link>
    <description>A few things to add.&lt;BR /&gt;&lt;BR /&gt;1. Never do this over NFS (unless you've got loads of spare time for `active waiting')&lt;BR /&gt;&lt;BR /&gt;2. find / -exec grep 'string' /dev/null {}\;&lt;BR /&gt; is good, but&lt;BR /&gt; find / -type f -exec grep 'string' /dev/null {}\;&lt;BR /&gt; is better (think pipes)&lt;BR /&gt;&lt;BR /&gt;3. GNU grep (available on &lt;A href="https://www.beepz.com/personal/merijn/" target="_blank"&gt;https://www.beepz.com/personal/merijn/&lt;/A&gt; or &lt;A href="http://www.cmve.net/~merijn/)" target="_blank"&gt;http://www.cmve.net/~merijn/)&lt;/A&gt; can do recursive greps&lt;BR /&gt; grep -r 'pattern' /&lt;BR /&gt; which is much faster and uses less system resources&lt;BR /&gt;&lt;BR /&gt;Enjoy, have FUN! H.Merijn</description>
    <pubDate>Mon, 06 Jan 2003 10:56:52 GMT</pubDate>
    <dc:creator>H.Merijn Brand (procura</dc:creator>
    <dc:date>2003-01-06T10:56:52Z</dc:date>
    <item>
      <title>find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874856#M99338</link>
      <description>I would like to find a file that contains a particular word (string) in the system ? Thx.&lt;BR /&gt;&lt;BR /&gt;eg. I would like to know which file(s) in the system contains the word ???Full??? , what can i do?</description>
      <pubDate>Mon, 06 Jan 2003 04:11:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874856#M99338</guid>
      <dc:creator>Cheung_2</dc:creator>
      <dc:date>2003-01-06T04:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874857#M99339</link>
      <description>find / -exec grep -l 'string to fine' {} \;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;This command will search the contents of every file in the system for the word in the single quotes.&lt;BR /&gt;&lt;BR /&gt;the / can be a subdirectory to save time.&lt;BR /&gt;&lt;BR /&gt;find command is very CPU/load intensive.  Use with care.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Mon, 06 Jan 2003 04:20:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874857#M99339</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-01-06T04:20:38Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874858#M99340</link>
      <description>find / -exec grep 'string' /dev/null {}\; &lt;BR /&gt;</description>
      <pubDate>Mon, 06 Jan 2003 08:18:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874858#M99340</guid>
      <dc:creator>Systeemingenieurs Infoc</dc:creator>
      <dc:date>2003-01-06T08:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874859#M99341</link>
      <description>what is the /dev/null do here on the find command?</description>
      <pubDate>Mon, 06 Jan 2003 09:07:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874859#M99341</guid>
      <dc:creator>Jason Tan</dc:creator>
      <dc:date>2003-01-06T09:07:02Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874860#M99342</link>
      <description>it forces grep to display the filename.  You could try it out on the /tmp to see the difference.&lt;BR /&gt;&lt;BR /&gt;if you do a 'find /', i might be wise to include a '-xdev', so it only searches your '/'.  In this way you can search each fs at a time, and avoid overkill.</description>
      <pubDate>Mon, 06 Jan 2003 09:19:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874860#M99342</guid>
      <dc:creator>Systeemingenieurs Infoc</dc:creator>
      <dc:date>2003-01-06T09:19:01Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874861#M99343</link>
      <description>A few things to add.&lt;BR /&gt;&lt;BR /&gt;1. Never do this over NFS (unless you've got loads of spare time for `active waiting')&lt;BR /&gt;&lt;BR /&gt;2. find / -exec grep 'string' /dev/null {}\;&lt;BR /&gt; is good, but&lt;BR /&gt; find / -type f -exec grep 'string' /dev/null {}\;&lt;BR /&gt; is better (think pipes)&lt;BR /&gt;&lt;BR /&gt;3. GNU grep (available on &lt;A href="https://www.beepz.com/personal/merijn/" target="_blank"&gt;https://www.beepz.com/personal/merijn/&lt;/A&gt; or &lt;A href="http://www.cmve.net/~merijn/)" target="_blank"&gt;http://www.cmve.net/~merijn/)&lt;/A&gt; can do recursive greps&lt;BR /&gt; grep -r 'pattern' /&lt;BR /&gt; which is much faster and uses less system resources&lt;BR /&gt;&lt;BR /&gt;Enjoy, have FUN! H.Merijn</description>
      <pubDate>Mon, 06 Jan 2003 10:56:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874861#M99343</guid>
      <dc:creator>H.Merijn Brand (procura</dc:creator>
      <dc:date>2003-01-06T10:56:52Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874862#M99344</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You may want to exclude binary files, so you could do something like this:&lt;BR /&gt;&lt;BR /&gt;find / -type f | xargs file | grep -v " shared " | cut -d: -f 1|xargs grep "string to find" /dev/null&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin</description>
      <pubDate>Mon, 06 Jan 2003 10:59:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874862#M99344</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2003-01-06T10:59:30Z</dc:date>
    </item>
    <item>
      <title>Re: find a string</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874863#M99345</link>
      <description>Hi Cheunq:&lt;BR /&gt;&lt;BR /&gt;I think u can find out each file(even each row in the file) in the system which contains the word(string) u specified by following command:&lt;BR /&gt;&lt;BR /&gt;find / -type f | xargs grep "Full"&lt;BR /&gt;&lt;BR /&gt;Good lucky!&lt;BR /&gt;&lt;BR /&gt;Tang qiang&lt;BR /&gt;&lt;BR /&gt;08/01/03</description>
      <pubDate>Wed, 08 Jan 2003 03:11:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-a-string/m-p/2874863#M99345</guid>
      <dc:creator>q tang</dc:creator>
      <dc:date>2003-01-08T03:11:40Z</dc:date>
    </item>
  </channel>
</rss>

