disable ADL log directory

[ljiang]

Hi,

Is there a way to disable the generation of log directories? I set "DBG_OFF", but still although log files are not generated, log directories with message.log and request.log are still being generated.

Thanks!

[bhenders]

Lide,

There is no easy way to disable the production of these additional file creations. I tried to point them to /dev/null in the light weight configuration file but that just causes an error to be thrown. I looked at the implementation and there isn't an easy work around that I can suggest. We could provide such a feature with additional software changes. The files are pretty small in nature, but I can understand the annoyance. If you feel strongly that we should fix this, could you send an email to Paul Meade indicating this. Paul can open a problem ticket that could be worked to disable the creation of these files.

Sorry, I don't have a better outcome for you.

Thanks,

Bryan Henderson
Raytheon Company

[ljiang]

Bryan,

Thanks for your reply. The issue here is that you need to clear these log files once in a while, otherwise if too many logs there will be error from ADL (due to random number overlap with each other).

Lide,

There is no easy way to disable the production of these additional file creations. I tried to point them to /dev/null in the light weight configuration file but that just causes an error to be thrown. I looked at the implementation and there isn't an easy work around that I can suggest. We could provide such a feature with additional software changes. The files are pretty small in nature, but I can understand the annoyance. If you feel strongly that we should fix this, could you send an email to Paul Meade indicating this. Paul can open a problem ticket that could be worked to disable the creation of these files.

Sorry, I don't have a better outcome for you.

Thanks,

Bryan Henderson
Raytheon Company

[bhenders]

In ADL 4.1, we added a time stamp as part of the log so that the chances of re-using a PID number would not cause a collission. It doesn't fix the problem of preventing the message.log and request.log file from being created, but you won't have the non uniqueness issue occur anymore or intermittent failures due to reusing the same PID number.

For example:

AdlEdrAlgorithmTemplate2.exe_20130301_150723_860898
AdlEdrAlgorithmTemplate2.exe_20130301_150723_860898.log

I'm guessing you aren't on ADL 4.1, but wanted to point out that your collissions will cease in that release with the log files.

Thanks,

Bryan Henderson
Raytheon Company

[bizzrisea431]

I have a batch file that logs the output of that file. how can i make the log that the batch creates save to a specific directory? thanks

[houchin]

I have a batch file that logs the output of that file. how can i make the log that the batch creates save to a specific directory? thanks

In cfg/DDSADL_CFG.xml, you can change the value of the property specifying the location of the log files to be entirely specified by an environment variable of your choosing, and then just set that environment variable before you run ADL. Here's how it's modified in AeroADL:

Code: Select all

         <!--
            name: DDS.ADL.DDS_DBG_PATH
            desc: The directory (relative path) for DDS debug files.
            units: N/A
            range: Any String 
            AEROADL_MODIFIED - Control debug log area entirely through an environment variable
         -->
         <config>
            <name>DDS_DBG_PATH</name>
            <configValue>${ADL_PACK_UNPACK_LOG_AREA}/</configValue>
         </config>

[ElijahMosley]

Thanks for your post