Replicating cclogd Problem

[Ivor Potter]

Hi

We have a third party application running on our system that I believe is incurring problems as a result of the well-cited problem with the cclogd. We are in the process of getting our system patched to resolve the daemon problem but before we do so we also want to prove that this is what is actually causing the problem with the 3rd party app.

My question then is - is there a way to force the cclogd to create the 11th file and move into its problem state? Our system currently has ccbootlog, ccbootlog.1 and ccbootlog.2 on it and is creating them at roughly 1 per day but we cannot afford to wait until it has created all 11 in its own time? I assume that dumping rubbish data into the logs to fill them up to 750Kb would corrupt the process - but what about copying ccbootlog.1 to ccbootlog.3; ccbootlog.4 etc so that when the process attempts it's next archive it will think that it is the eleventh one?

Thanks in advance

Ivor