Mark Hazen wrote: > Mark Hazen wrote: > >>>I wish this were true, but no one will ever get IO::Scalar to catch DBI's >>>STDERR output. >>> > >>If so, it's only because STDERR under mod_perl is already tied. DBI is >>not an external process. >> > >>>Throwing all this stuff into a file is already something DBI >>>can do, but as I already said, opening several hundred files per minute >>> > will > >>>overwhelm my system. >>> > >>I don't think it does that. It should open one file per process that >>has tracing turned on and keep writing to it. I already suggested that >>you can just turn it on for a single process. That would mean one file >>being written to by one process, which is very unlikely to overwhelm any >>system. >> > > That's your opinion. In my opinion, a bunch of disk IO and file seeks are a > waste of resources. The bigger issue here is that it is better to store in > memory, and it saddens me that it doesn't seem possible.
Hmm, then create a ramdisk and read from the file virtually stored in the RAM. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
