Changing the log directory for ADL unpacker

[houchin]

Is there a way to specify the log file directory for the ADL unpacker without mucking with the code itself? Maybe something similar to changing the output directory?

[kbisanz]

In the file $ADL_HOME/CMN/Utilities/DDS/cfg/DDSADL_CFG.xml you can change the value for "DDS_DBG_PATH". That changes the log directory for the stand alone unpacker and packer, as well as the packer log file produced when an algorithm runs and produces HDF output. The regular algorithm debug log (ending in .log) will still be $ADL_HOME/log.

Note that for the value of DDS_DBG_PATH, you do need a trailing slash. I've added the requirement for the trailing slash to the list of issues to fix. The development of ADL 3.1 is almost done, so I'm not sure if it'll be fixed in ADL 3.1 or not.

[houchin]

I tried that directory but it didn't work. Is that just the base file used to populate $ADL_HOME/cfg when you build?

Changing it in $ADL_HOME/cfg did work though.

[kbisanz]

In our configuration management system, a lot of code is reused from the operational system. Rather than copy the code, there are symbolic links to it. So, $ADL_HOME/cfg/DDSADL_CFG.xml is actually a link to $ADL_HOME/CMN/Utilities/DDS/cfg/DDSADL_CFG.xml. When I changed CMN/Utilities/DDS/cfg/DDSADL_CFG.xml the change was also reflected in cfg/DDSADL_CFG.xml.

However, when we package ADL to ship, we basically go to $ADL_HOME and tell tar to resolve all links (the -h option). This has the advantage of making the packaging simpler and it ensures that we don't ship dangling sym links. However, it does break the link between linked files like that.

I apologize for giving the incorrect file name. Hopefully you didn't spend too much time figuring it out.