Only log files that reach 90% of their size limits are backed up, and the original log file is emptied.
The size limits for the log files are defined in $NMSROOT/conf/logstat.conf with values in bytes. So if a log file has not reached 90% of this predefined value OR is even not listed in this file it will not be touched be logBackup.pl (on Windows, some log files are also defined in the registry)
logBackup.pl was the first utility to handle log file size, but the daemon manger must be stopped to execute it. I would recommend to configure logrot.pl instead to handle log files and have the daemons running. See the above online help link to get details about logrot.pl and also search this forum - there are multiple threads with this issue.
If you have configured logrot.pl properly you do not need to delete log files manually.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.