<?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 command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436546#M5301</link>
    <description>how many mpeg files are there, there may be too many to pass to the wild card, in whcih case write a simple loop to pick up the files.</description>
    <pubDate>Tue, 15 Aug 2000 13:26:11 GMT</pubDate>
    <dc:creator>Scott Dunkley</dc:creator>
    <dc:date>2000-08-15T13:26:11Z</dc:date>
    <item>
      <title>find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436541#M5296</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When executing the find command as in the example below, the command appears to terminate prematurely.  At times, depending on what I am searching for I do get some returns, but inevitably the command terminates the same way without completely searching the directory hierarchy.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any ideas?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!&lt;BR /&gt;Peter&lt;BR /&gt;&lt;BR /&gt;EXAMPLE:&lt;BR /&gt;&lt;BR /&gt;ns01# find . -name "*.mpeg" -exec rm -i {} ;                                   &lt;BR /&gt;find: cannot open .: Value too large for defined data type                      &lt;BR /&gt;ns01#</description>
      <pubDate>Tue, 15 Aug 2000 11:32:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436541#M5296</guid>
      <dc:creator>Peter J. Palmquist</dc:creator>
      <dc:date>2000-08-15T11:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436542#M5297</link>
      <description>Do you have a "hidden" directory there somewhere? (eg. one with say space for a name?)</description>
      <pubDate>Tue, 15 Aug 2000 11:41:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436542#M5297</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-08-15T11:41:00Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436543#M5298</link>
      <description>Your comand is okay. If the kernel parameters for maxssiz, maxtsiz and maxdsiz are default sizes as at when system was installed, pls increase them.</description>
      <pubDate>Tue, 15 Aug 2000 11:47:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436543#M5298</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-08-15T11:47:13Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436544#M5299</link>
      <description>Peter:&lt;BR /&gt;&lt;BR /&gt;This is common if there are a large number of arguments.  You can avoid this by using xargs in place of exec.  This is actually "kinder" on system resources.  Do something like:&lt;BR /&gt;&lt;BR /&gt;# find . -name "*.mpeg"|xargs -n100 rm -i {}&lt;BR /&gt;&lt;BR /&gt;This will do 100 files at a time until the list is exhausted.&lt;BR /&gt;&lt;BR /&gt;See the man pages for xargs.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 15 Aug 2000 12:32:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436544#M5299</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-08-15T12:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436545#M5300</link>
      <description>Peter,&lt;BR /&gt;&lt;BR /&gt;Just working on a hunch, are any of the *.mpeg files greater then 2GB in size?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Aug 2000 12:33:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436545#M5300</guid>
      <dc:creator>Trevor Dyson</dc:creator>
      <dc:date>2000-08-15T12:33:32Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436546#M5301</link>
      <description>how many mpeg files are there, there may be too many to pass to the wild card, in whcih case write a simple loop to pick up the files.</description>
      <pubDate>Tue, 15 Aug 2000 13:26:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436546#M5301</guid>
      <dc:creator>Scott Dunkley</dc:creator>
      <dc:date>2000-08-15T13:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: find command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436547#M5302</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Thanks a bunch for all your help!  Chris &amp;amp; James the comments you made helped me isolate the problem.  The homes which I had to clean reside on a Network Appliance, and are mounted to an Intel Box running Solaris.  When I instead mounted the Network Appliance to my HP B2000 running HP-UX 11.0, I was able to perform my searches without any problems at all.  The comments about the kernal perameters are what clued me in to making this change.  Thanks again!&lt;BR /&gt;&lt;BR /&gt;Peter</description>
      <pubDate>Wed, 16 Aug 2000 11:07:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/find-command/m-p/2436547#M5302</guid>
      <dc:creator>Peter J. Palmquist</dc:creator>
      <dc:date>2000-08-16T11:07:34Z</dc:date>
    </item>
  </channel>
</rss>

