Skip to content
Snippets Groups Projects
Commit 5e78f357 authored by Brutzman, Don's avatar Brutzman, Don
Browse files

add url as comment

parent 40d939b5
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
examples/pduLog/README.md
+ 3
− 1
View file @ 5e78f357
...@@ -2,6 +2,8 @@ ...@@ -2,6 +2,8 @@
This directory holds temporary PDU log files which may be deleted at any time! This directory holds temporary PDU log files which may be deleted at any time!
To clean out old log files, simply run [build.xml](build.xml) target `clean.all.log.files`
Each time you run a DIS simulation and a PduRecorder is listening, another Each time you run a DIS simulation and a PduRecorder is listening, another
log file is created. File names are numbered sequentially and uniquely, so that log file is created. File names are numbered sequentially and uniquely, so that
important PDU log captures can later be copied and saved to where they are needed. important PDU log captures can later be copied and saved to where they are needed.
...@@ -14,4 +16,4 @@ the corresponding homework or project directory (and likely renaming as well). ...@@ -14,4 +16,4 @@ the corresponding homework or project directory (and likely renaming as well).
Note that the PDU log files are very tolerant of inline comments starting with Note that the PDU log files are very tolerant of inline comments starting with
a # character, so you can document success/failure and TODO issues there as well. a # character, so you can document success/failure and TODO issues there as well.
To clean out old log files, simply run [build.xml](build.xml) target `clean.all.log.files` <!-- https://gitlab.nps.edu/Savage/NetworkedGraphicsMV3500/-/blob/master/examples/pduLog/README.md -->
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment