Actually, it might have a LOT to do with client variables. An export of our
Solaris registry right after setup was less than 8KB, three weeks later, it
was several MB in size, all due to a programmer who inadvertently turned on
client vars when he meant to only enable session vars. CF doesn't purge
client vars for 90 days, so needless to say, the registry can get REALLY big
in a hurry on a busy website. Note that nothing actually set any client
vars, the entries were just for the CFTOKEN and CFID. The Solaris server is
reasonably stable as long as the registry file is kept small, and without
clent vars, it will stay small.
Summary:
If you're using client vars, get them into a database. If you're not using
them, make absolutely sure they're not enabled anywhere. Export your
registry, the only client var entries you should see will be from use of the
CF Administrator application. (Though why in all of heaven and earth they
are enabled there, I'll never know.)
Michael J. Sheldon
http://www.desertraven.com/
Make a fast friend, adopt a greyhound!
-----Original Message-----
From: Ed Toon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 19:09
To: [EMAIL PROTECTED]
Subject: RE: Client storage (RE: ColdFusion 4.0.1/SPARC/Solaris help
sought - registry corruption and cf scheduler problems)
This has nothing to do with client variables. Cold Fusion uses the Registry
a great deal itself internally. For example, all datasource info, scheduled
tasks, etc...
----------------------------------------------------------------------------
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
