>
> We seem to be making some progress but the server still doesn't seem
right.  We setup a MySQL
> database and have set this to store all Client Variables.  We then removed
from the 'registry'
> folder (in opt/coldfusion) all the random files that had been created
leaving just 'cf.registry' and
> 'cf.registry.template'.  Restarted the machine and it has instantly made
two more random files and
> now look like this:
>
> -rw-------   1 coldfusi bin      26681822 Jan 14 13:34 cf.registry
> -rw-------   1 coldfusi bin          1829 Jun 13  2001
cf.registry.template
> -rw-r--r--   1 coldfusi bin             0 Jan 14 13:35
file0mcPW4.-1125748503
> -rw-r--r--   1 coldfusi bin      18145539 Jan 14 13:41
filenMv5aj.-1125398939
>
> How can we get rid of these files and reduce the size of 'cf.registry'?
>

Michael Dinowitz wrote a registry cleaning tag some time ago.  You can find
it here :
http://devex.macromedia.com/developer/gallery/info.cfm?ID=CA347269-2830-11D4
-AA9700508B94F380&method=Full
In the dev exchange.....

Ah....  Just realised.... its a CFX.....
Ermmm.... I'm not sure exactly what Michael's tag does, but I suspect it
just removes the registry entries for the client variables. They are stored
under
"hkey_local_machine\software\allaire\coldfusion\currentversion\clients\", so
you can more than likely just use cfregistry to have a read through and
delete of all the entries stored under there.

Another solution is to edit the file by hand, but that's not feasible with a
file 20mb in size....


Hope this helps

Regards

Stephen


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=14
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=14
This list and all House of Fusion resources hosted by CFHosting.com. The place for 
dependable ColdFusion Hosting.

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
                                

Reply via email to