[Jon Stratis]

What about creating a new log file each time? That's how things are handled with the server production systems I work with - each log file has a timestamp as part of the file name to help prevent overwrites.

I'm not sure how the clock works on the cRIO or what level of access we have towards getting a standardized timestamp, but there are other options as well. For example, you can have each log file generated with an incrementing numerical value (1.log, 2.log, etc). Keep the current value in a config file (log.config). When the program starts up, it reads the config file, increments by 1, writes the new value out to the config file (overwriting the old value) and creates the log file using that value.

This has the added benefit of giving you a separate log file for each run, which will help you keep everything organized.