Sametime trace folder grows un-expectedly

Excessive amount of logs are generated in the trace file and this invades a lot of space in memory

Windows 2003, 2008 (32 or 64 bit)

Tuning sametime.ini and finding those parameters then deleting them.

Steps for resolving Sametime trace folder grows un expectedly

1) in SametimeDiagnostics.properties, change

com=50
com.lotus=50
com.ibm=50

to be instead default value of 30;

com=30
com.lotus=30
com.ibm=30

2) Remove any un-necessary logging.

In this instance we seen these two parameters below:

ST_TRACEFILE_SIZE=3
ST_TRACEFILE_CNT=10

It was recommended to remove these, and we have explained the nature of these .ini parameters below

Explanation of these parameters

ST_TRACEFILE_SIZE=file_size - Sets the maximum file size of each trace file.
ST_TRACEFILE_CNT =number_of_files - Set the number of trace files generated per Sametime service application.

ST_TRACEFILE_SIZE multiplied by ST_TRACEFILE_CNT equals the maximum size of the trace files on the Operating System hard disk per Sametime Community Service Application.

Example
If the sametime.ini contains the following settings:

ST_TRACEFILE_SIZE=10
ST_TRACEFILE_CNT=25

Then 10 X 25 equals 250, so 250 MB is the maximum disk space each Sametime Service application consumes for the trace files

3) Stop the Sametime server
4) Delete the contents of the Sametime trace folder
5) Restart the Sametime server
6) Confirm are there excessive amounts of files still being generated in the Sametime trace folder?
You can check this via means of a trace directory listing (complete with date time stamps + file sizes)