Is this a feature that would be useful? Currently TurboFloat Server continues appending to the end of the file. It never deletes it or moves it.
Does the TurboFloatServer clean up its logs periodically?
If the TurboFloatServer is installed as a Windows Service, I could imagine that the log file (with the logging set to "notification") could get really long eventually. Does the TurboFloatServer clean up its own log file automatically (such as deleting entries 15 days old or something like that), or does this need to be done manually by the local IT staff?
I would think so, though I guess it isn't that high of a priority. Perhaps you could delete the lines that are 30 days old or something so that the log file stays at a reasonable size. Maybe set the amount of days before deleting an entry in the config file.
The issue is that I plan to deploy the TurboFloatServer with logging set to "notification" by default. This means that the log file could get decently large (for a text file) over the course of several months. This isn't so much an issue of the size of the file on disk (at least not in my case, that is) but the ease of examination of the file in a text reader. I suppose if the IT people decreased the lease interval to something significantly less than 30 minutes, then the log file could get huge in only a month or so.
Hmm, I don't know about deleting lines -- that probably isn't the best solution. Maybe we'll add something like log rotation (let the customer specify, in the config file, some period to "archive" old log files). We'll have to think about the best way to do this.
Sounds good. Thanks.