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

19990322: ldm & scriptconfig

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: 19990322: ldm & scriptconfig
  • Date: Mon, 22 Mar 1999 10:06:48 -0700
>From: address@hidden
>Organization: St. Cloud State
>Keywords: 199903221537.IAA29874 scriptconfig PATH

Alan-

>Just a short followup on your comments from 3/21 on scriptconfig.
>
>I recall you made a similar comment to me during our first setup of
>ldm a few weeks back; i.e. that scriptconfig is supposed to find perl
>on its own.  

I guess I need to correct myself.  scriptconfig will find perl if
the directory containing perl is in the user ldm's path.  Apparently,
/usr/local/bin is not in ldm's path on your system, so it couldn't
find perl.

>Regarding this latest setup, perl had been installed properly, using
>pkgadd, and was in usr/local/bin, as /usr/local/bin/perl.
>Why do you think we got the error message when we first ran scriptconfig?
>My sense is that it did not find perl on its own, but things worked fine
>when I listed the full path name.

I stand corrected.

>My student did this step initially (run scriptconfig), but I think he was
>following the steps in your binary install writeup, as we have printed copies 
>of these files from your http address.  
>
>At any rate, do you suspect other things have been messed up as a  result
>of our editing and re-running of scriptconfig?  

Nope, you did the correct thing for your setup.  However, it would probably
be a good idea to add /usr/local/bin to ldm's path to find things like
gzip and gcc if needed.  You should do the same for the user mcidas.

Don