Is a large log file a problem?

[Misfit_ha 0]

Will a large .rpt file cause problems down the road even if most things look fine in smaller tests we've done?

log file size is 1.85mb

https://paste.ofcode.org/jTcyRe9SyeLH5tE2AsqsmE

[Gunter Severloh 4054]

A large rpt wont be a problem or effect performance of a server until your running a mod, or mission with

a conflict that spams the rpt, when the list becomes a mile long and ever keeps growing then you might or could

experience issues ingame.

    Imo if your not testing to see if a mission is running with mods, or mods are working, or if a mission you put on

your server is working, or trying to determine a mod conflict then just turn the logs off until you come across a problem.

it all depends what your running and or playing.

[Tankbuster 1746]

1.85 MB? Those are rookie numbers. A large logfile isn't a problem as such, frequent writing to the file can cause issues.
A mission that has been running for a long time (more than a few days) can accumulate a large logfile because there's a lot of stuff that the game writes to the logfile normally.
Because writing the logfile is an I/O operation that is expensive on RAM and CPU, lots of logfile entries being written in a short time is a problem. A script error or some other issue that writes the logfile more than a ~20 times a second can have an impact on performance.

[Tankbuster 1746]

I've had a quick look over that RPT. You use a lot of addons and you use some that I'm not familiar with. I don't use CUP or ACE3 for example.

You use CUP Terrains core, but the RPT at line 158 onwards seems to say you're missing some required CUP addons.

Also, clients are executing functions that are not allowed by class CfgRemoteExec. That's causing a lot of RPT spam