[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050421: LDM scour issue and computer lock-up

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20050421: LDM scour issue and computer lock-up
  • Date: Thu, 21 Apr 2005 10:03:37 -0600
Gabe,

>Date: Thu, 21 Apr 2005 11:52:07 -0400 (EDT)
>From: Gabe Langbauer <address@hidden>
>Organization: Ohio State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050421: LDM scour issue and computer lock-up 
>Keywords: 200504191903.j3JJ3u4n010376

The above message contained the following:

> No output

That means it worked.

The problem is the setting of the PATH environment variable near the top
of the scour(1) script.  As distributed, the script should have this:

    PATH=/bin:/usr/bin

Your script, however, has this

    #PATH=/bin:/usr/local/
    PATH=/bin:/home/ldm/bin

Apparently, the find(1) utility is in the /usr/bin directory and without
that component in PATH, the shell can't locate that utility.

I suggest that you add /usr/bin to PATH in your scour(1) script.

Regards,
Steve Emmerson