I am sure this has been asked before but in CW syslog.log just keeps on getting bigger and bigger. I have set the log rotation parameters to 2GB with no backups. The file is currently 2.5G (it can get upto 10G before we notice problems with CW and have to manually delete the file).
From some of the threads I have read on this topic at CSC it seems once we have configured the maximum file size we then also have to set a periodical surge policy to empty the file - is this correct? If so, then this two stage procedure seems counter productive. Isn't the whole point of specifying a file size is that once it reaches that limit the contents are cleared and the counter reset to zero hence the name 'log rotation'. And if we have to set a periodical surge policy seperately then the file size limit should become irrelevant because the file is being surged regardless of its current size. Am I right or am I missing something?
We are using LMS 3.2.
Log rotation alone should take care of syslog.log. Post the NMSROOT/objects/logrot/logrot.conf file, and the output of the following command when the syslog.log file is above your configured threshold:
NMSROOT/bin/perl NMSROOT/bin/logrot.pl -v