I've experienced the <cfexecute> problem where if you: (1) Don't specify an output file (2) Get a long output (>4K, I think) from your executable then you get a hung process on your server, requiring the kill (process) command.
Does this problem still occur if you *do* write an output file? Any workarounds either way? I ask, because I'm trying to determine the best way to schedule Verity K2 indexing jobs (through cfschedule or AT). CF5, BTW. Thanks, Jamie ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
