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

Re: ldm upgrade...acting odd

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: Re: ldm upgrade...acting odd
  • Date: Thu, 16 Jun 2005 17:40:21 -0600
Gabe,

>Date: Thu, 16 Jun 2005 18:19:21 -0400 (EDT)
>From: Gabe Langbauer <address@hidden>
>Organization: Ohio State University
>To: Steve Emmerson <address@hidden>
>Subject: Re: ldm upgrade...acting odd 

The above message contained the following:

> I know that the old pqact is being used because (the most obvious thing) 
> the continued creation of data in the data/EXP with the suffix _old  This 
> call was created as a test to try to figure out which pqact was running.

That would work IF the old and new pqact(1) utilities used different
configuration-files.  By default, they both use the non-version-specific
configuration-file $HOME/etc/pqact.conf.  In the LDM configuration-file
that was being used by the version 6.1.0 LDM, did the pqact(1) EXEC
entry explicitly specify a pqact(1) configuration file?

If not, then you might be confusing an "etc/" subdirectory in a
version-specific subdirectory with the version-independent one in the
LDM user's home directory.  Version-specific subdirectories should not
contain "etc/" subdirectories (but did in your case).

Regards,
Steve Emmerson