We're running LMS 2.6 (CS 3.0.5, RME 4.0.5, CM 4.0.6) on Windows and our syslog.log is now around 98GB. The disk has about 10GB free remaining. I attempted to run logrot.pl set to 0 archives, hoping it would blow away the huge file and create a smaller one for us. Instead, I got this error message: "WARNING: Failed to get a successful value back from D:\PROGRA~1\CSCOpx\bin\logrot_stat.exe, using Perl stat instead (note: this will fail for files > 4GB)". I've heard erasing the syslog.log file causes more problems; what can I do to eliminate this monster and start afresh with a new syslog.log?
Report? If this becomes more of an emergency, you can run NMSROOT\bin\logrot_trunc.exe NMSROOT\log\syslog.log to truncate the file without shutting down dmgtd. However, I'd like to find out why the stat helper is not able to ge tthe size of this file.
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.