I'll just offer a counterpoint for folks to consider. :-) While Cam talks about the benefits of running CF from the command line (with the console output dumped to screen), I'll say that I don't myself like to do that for the very reason that I like the logs. I don't like that when the instance dies, all the info that went to the console is lost.
For those who never noticed, the console output is logged by default to a coldfusion-out.log (or instance-out.log) when CF is not run from the command line. These -out.log files are stored in the [jrun]/logs in multiserver deployments and in [cf]/runtime/logs on Standard or Server deployments.Many mis them when they can in fact be quite vital to solving problems (whether in development or production). I realize of course that Cam is talking about running from the command line in development, and he's ok with reviewing the info as it appears in the console. I just prefer even in development to have access to the info after the fact. Different strokes. :-) Just wanted to share that observation if it may help some readers. (And to be clear, when I mentioned starting the service from the command line, that does NOT cause the creation of a console interface. The logs are created when CF is started with the jrunsvc command, which starts the service. What Cam is talking about now (and I above) is when one starts CF with the JRUN command instead.) Hope that's helpful. /charlie > -----Original Message----- > From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Cameron > Childress > Sent: Tuesday, December 08, 2009 1:52 PM > To: discussion@acfug.org > Subject: Re: [ACFUG Discuss] ColdFusion debugging info > > On Tue, Dec 8, 2009 at 10:25 AM, Charlie Arehart <char...@carehart.org> > wrote: > > You may prefer to do this from the command line (or a shortcut) > instead. > > While there are also jrunsvc options that could allow you to > stop/start the > > instances Service from the command line as well, what I do instead > is > > simply create a shortcut that calls the Windows services controller > > (net.exe) itself: > > To further expand on this, here's what I do... For development on my > own local machine I set any CF Windows Services to manual so they > don't start with the machine. I then use .bat files to start cfusion > instances when I need to. I have startup scripts for CF7, CF8, and > CF9 instances, some configured for specific clients. I have maybe 10 > or so instances in all. I've created a folder on my Windows > QuickStart bar and dropped all the bat files in it. > > When I want to startup a specific instance I just click the folder and > select the instance I'd like to start. I start them in a console > window, which also has the added benefit (for me) of showing any > errors right there in the window. This means I don't have to look for > logs when something silently fails, I just look at the console output. > You can also set Flex Remoting data to dump into the console if you'd > like to see it. Server needs a restart? "CTRL+C" the console to stop > it and then run the bat file again. > > There are other ways to accomplish these same things, but that's what > I have gotten comfortable with over the years... > > -Cameron ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
