NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi, Just to clarify, pqact(1) will interpret a relative pathname of its configuration-file relative to the home directory of the LDM installation ($LDMHOME). With the advent of the LDM registry, pqact(1) interprets relative pathnames of FILE actions relative to the LDM registry parameter "/pqact/datadir-path" (the default is determined by the configure(1) script and is "$LDMHOME/data" if that directory exists and "$LDMHOME/var/data" if it doesn't). Execute the command "regutil /pqact/datadir-path" to see the value of this parameter. Regards, Steve Emmerson On Fri, Aug 22, 2014 at 8:49 PM, <wxprofessor@xxxxxxxxx> wrote: > e > >> This is exactly what I thought and how I have the structure based. But >> the system still isn't seeing files set in the sub-directory relative to >> the home directory. This means my problem lies elsewhere and that is a HUGE >> help. >> > > you probably do not have your environment variables setup appropriately... > if you use bash as your default shell this would be .bash_profile in your > user's root directory.. or .login for csh. > > note emmerson's notes here, under 'steps to perform as ldm user' > > http://www.unidata.ucar.edu/software/ldm/ldm-6.12.4/ > basics/preinstallation.html > > > > > _______________________________________________ > ldm-users mailing list > ldm-users@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ >
ldm-users archives: