Check your registry file /opt/coldfusion/registry/cf.registry. Are you storing client variables in the registry? If so, you should stop.
The flat-file implementation on Unix is very inefficient. Cfexec is trying to expire client variables (default is 90 days) when its starts up. This is probably what is chewing CPU (i.e. it is working). -- Tom Jordahl Macromedia -----Original Message----- From: Mark Leonard [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 15, 2001 2:47 PM To: CF-Linux Subject: RE: cfexec taking huge amounts of resources and dying > -----Original Message----- > From: Debbie Dickerson [mailto:[EMAIL PROTECTED]] > Sent: November 15, 2001 12:35 Late > To: CF-Linux > Subject: RE: cfexec taking huge amounts of resources and dying > > > I think he's referring to the service, not the tag. > > The executive service could be doing a few things: > --Do you have any scheduled tasks that would be running? > --Any mail in the spool directory that needs to be sent out? > --Client variables that need to be expired? > > At least check out your executive.log to see if there are any errors being > reported. > Yeah, I meant the service. The mail spool directory is empty, and the executive.log doesn't show anything other than when I restart it after it dies.. =/ As soon as coldfusion starts, it takes up that amount of cpu, and it's death period has been getting smaller and smaller over the last day.. There aren't any scheduled tasks, as far as I know. Would client variables get reloaded after a restart of coldfusion, or are they volatile? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com ------------------------------------------------------------------------------ Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
