A little more information:
If your sensor is not configured for summer-time, then your sensors will not hit CSCsa85330.
If your sensor is running version 4.x, then your sensor will not hit CSCsa85330.
But if you sensor is version 5.x, and configured for summer-time with the default settings which are used in most locations in the United States and possibly other countries. Then your sensor is likely to hit CSCsa85330.
If you are unable to install the 5.0(5) Service Pack you may want to consider disabling summer-time on your sensors before this coming Sunday when the switch over happens.
What happens if your sensor does not get upgraded before Sunday and you are using the summer-time option for handling DayLight Savings Time:
The mainApp process will core sometime during the 24 hours after the switchover happens.
With the mainApp core you will no longer be able to ssh or telnet to the sensor as the cisco userid, or any other userid with administrator, operator, or viewer privelage levels. Any monitoring tool pulling events from the sensor will loose connection to the sensor because the connection is through the web server that is part of mainApp.
How to recover:
If you have a service account, then login using the service account. Switch to user root using the command "su -" and provide the same password for root as for your service account.
As user root you will then need to execute "reboot" to reboot the sensor.
NOTE: The service account unlike the other accounts can still login even after the mainApp crash.
If you do not have a service account then the sensor will need to be rebooted by another means. If the snesor is an appliance you will need to physically power the sensor on and off. If the sensor is an IDSM-2, NM-CIDS, ASA-SSM-10, or ASA-SSM-20, then you will need to login to the switch, router, or asa and reboot or reset the module.
I will keep you posted of any other developments, and let you know when the 5.0(5) Service Pack is available.
