CiscoWorks might not run if the size of the Syslog.log or syslog_info file is huge.
To resolve this issue, perform these steps:
This really sounds like a Windows Explorer behavior and not an LMS issue as it sounds like the messages are being received.
Perhaps something like http://tailforwin32.sourceforge.net/ would be of use to you.
Here are some notes about changing the syslogging location:
1. Stop the syslog daemon in Control Panel-->Administrative Tools-->Services (CWCS/CMF Syslog Service)
2. Stop the Syslog Collector via the command line on DOS: cd C:\progra~1\CSCOpx\binpdterm SyslogCollector
3. Create the new syslog.log file (say d:\ciscoworks\syslog.log), ensure that casuser has full access to this file.
4. Open the Registry (Regedit) HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Crmlog\Parameters Right mouse on this "LogFile" line-->Modify Note: If you want to change the default Syslog Message Sourcelocation, you must first set the new location in the Windows Registry and only then change the Message Source location in the RME-->Administration-->SyslogAnalyzer-->Change Storage Options dialog box.
5. Use an editor and modify the entry for: SYSLOG_FILES= in $NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Collector.properties
6. Start the Syslog daemon in Services (see step 1).
7. Start SyslogCollector Process via CLI on DOS:pdexec SyslogCollector
8. Update the location of the syslog.log file in the logstat.conf file. (The logstat.conf file is located at CSCOpx/conf.) This ensures that the new syslog.log file is referenced when you generate a Log File Status report (Common Services --> Server -->Reports --> Log File Status).
Can we disable the CWCS syslog service permanently if we are not using the Syslog feature in Cisco LMS?