Posted by Robert G laurin on August 15, 2007 at 07:40:30:
Following our still-unresolved issue with directories using latest & greatest CFAM, we changed the settings in the CometServe Console screen to log ALL messages. In no time flat we had a log file that was well over TWENTY GIGABYTES (20 GB). Needless to say that the Comet Services folder being on the C: drive on the server caused many softwares & windows logs to fail for lack of space. This is real bad on a server with a TERABYTE of disk space available.
I tried opening the CometServe Console and it took 20 minutes for the log to load in the ListBox (all other controls frozen solid for lack of multi-threading).
I hit the ClearLog option in the File menu, it cleared the ListBox dialog but failed to clear the actual Log file on the C: drive. I am still stuck with a 20GB monster that I can't rid of. With over 80 users connected (including XAP & Anywhere), rebooting is not an option.
Oddly, when I close & open the Console, the messages do not show up anymore - even if the file is still there in it's full glory.
So I ask,
Should the logs file be cleared when we clear the logs?
Why is the CFAM Log option un-available in the drop down menu?
Shouldn't we have the option to select a different file location? Program Files/Signature Systemes Inc/Comet Services is not an ideal location for a log file. How about E:\Terabyte\Comet.Log ?
The Console alse gives option to override default settings (no of files, no of connection, extract entries, etc...). Shouldn't there be some statistics to tell us how much is actually used and what is the maximum ever used?