Re: Searching the IFS

[Larry Bolhuis <midrange@xxxxxxxxxxxx>]

Only 10 minutes and you quit? Do remember that these sort of commands 
can run for a LONG time especially if you have a lot of directories! 
Watch active jobs and you'll see the find command running in a different 
job.

I agree that Dennis' command does work.

 - Larry

PS Glad you found it anyway!!


Jon Paris wrote:
> *This message was transferred with a trial version of CommuniGate(r) Pro*
> Thanks Dennis,
>
> I still can't make it work.  Even if I start in root and give it the  
> names of two directories I know to exist it comes straight back with  
> nothing.
>
> As I was in root I figured that maybe removing the leading "/" would  
> be required.  That certainly dind't come back right way - some 10  
> minutes later it still hadn't come back so I canned the shell  
> session.  I guess I'm just going to have to learn all this Unix c$%p  
> because I need it more each day.
>
> Thanks anyway - luckily Susan found what we were looking for by a more  
> brute-force approach!
>
>
> Jon Paris
>
> www.Partner400.com
> www.SystemiDeveloper.com
>
>
>
> On 27-Sep-09, at 7:07 PM, midrange-l-request@xxxxxxxxxxxx wrote:
>
>   
> > So after that last reply I had a nice dinner, and came up with an
> > alternative that is more precisely what you requested:
> >
> > Find . -type d | grep -i '/myDirName/mySubDirName/$'
> >
> > This has the advantage that it is not subject to the imperfect
> > implementation of mixed-case support inherent to QSH (the -i flag  
> > sees to
> > that).  Also, unlike the prior solution, it won't report false  
> > positives
> > (such as dir1/myDirName/x/y/mySubDirName).  And finally (perhaps more
> > importantly), it makes you right about the need for grep.  ;)
> >
> > HTH
> > Dennis
> >     
>
>