I spent 2-3 hours troubleshooting this! With so many ARMA 3 servers running, one would think this bug would have been fixed by now or the documentation corrected. Also, I think miliseconds is misspelled within the log file, and should be "milliseconds". Other minor nuances are the .rpt files should be suffixed ".log" files. And the names of the log files should be standardized to omit the difficult to type underscores (ie. _) characters, unless absolutely required.

CURRENT: arma3server_2016-06-21_01-29-14.rpt

SHOULD BE arma3server-20160621-0129.log

And omit the seconds as typically I've rarely seen such log files including seconds within their naming schemes. The seconds field also only increases the confusion when typing such files via the command line or elsewhere. (Usually I'm only looking at the last to characters of log files, which is typically the minutes field.) I've seen some log file names include colons, but again these are further difficult characters when typing via the command line or console. All the previously mentioned issues adds further overhead or additional time for debugging. My current debugging environment uses two shells/consoles (ie. CygWin), one running console executing the arma3server.exe and the other console using "tail -f" to monitor real time output.

Shrugs... For now, at least there are no blank spaces within the log file names.

A very minor nuance, single characters use single quotes (ie. '), while more than one character values usually get double quotes. (ie. ")