How to change the JRun log files location

I recently set up a virtual server with hostmysite.com and we installed our own copy of ColdFusion Enterprise. In the process, I wanted to follow hms's guidelines about putting all log files on the E: drive as opposed to the default C: drive where ColdFusion gets installed. Now I'm not entirely certain why they're so adamant about the segregation (beyond the obvious security considerations of growing log files impeding the smooth operation of the OS), but I am personally concerned about the lack of hard drive space on the VPS. There's only 2 gigs allocated to the C: drive, and after loading it up with ColdFusion (two instances), MSSQL 2005, Subversion (repos on a different drive), and some other tidbits, I'm down to only 750 MB free. Another production server I manage has almost that much taken up in the JRun log files alone!

It's easy enough to use the ColdFusion administrator to move the ColdFusion log files (like application.log and server.log, etc), but I really need to move the JRun-specific log files, namely default-err.log, since that's the one that grows bit-by-bit whenever an error is thrown in CF (including those pesky "java.net.SocketException: Connection reset").

You can't use the CF administrator to modify the location of those log files, but you can use regedit to do so. The key is in

If you have multiple CF instances, you'll have to make the change in each key, where "Macromedia CFMX AS cfusion" above is the Windows service name. For a single-instance, standalone ColdFusion installation, the key would be in

Change the "SystemErr" and "SystemOut" values from

to

and bounce the service. Voila! You don't need to shuttle the log files by hand. When the service starts, new log files will be created in the new location. You can do this for the -err and -out logs.

If you're on hostmysite's VPS plan that includes CF, you may want to make this change yourself. The default image for the CF VPS plans don't put these log files on the E: drive, which means you could run out of room on the C: drive in a relatively short amount of time, depending on traffic and your application's profile.