Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

barbie (2653)

  reversethis-{ku. ... m} {ta} {eibrab}

Leader of [] and a CPAN author []. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [] and the QA Hackathon [] websites. Also the current caretaker for the CPAN Testers websites and data stores.

If you really want to find out more, buy me a Guinness ;)

Memoirs of a Roadie []
CPAN Testers Reports []
YAPC Conference Surveys []
QA Hackathon []

Journal of barbie (2653)

Tuesday September 20, 2005
04:08 AM

eval and file handles

[ #26798 ]

I have been running some code for quite some time, but each time there is an eval failure, the audit log stops getting written to. The code loop continues and the eval is called again for other entries, but the audit trail in the file stops dead. The messages are still printed to the screen, but just not to the log file. I open and close the file handle for each set of messages, so even a buffering problem shouldn't exist. This is running on Windows so I am now wondering whether there is something specific about Windows that an eval interrupt effects file handles.

I've been meaning to look at Log4Perl for sometime, so perhaps now is that time, and see whether it makes a difference. I certainly haven't found anything via Google, but then I could be asking the wrong question :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Have you tried reducing the code to the smallest portion that exhibits the problem? If that didn’t help you, can you post it?

    Otherwise, all anyone can do is guess. :-)

    • It's actually part of CPAN::YACSmoke. As such it may also be something to do with the way that CPANPLUS uses select. I haven't tried to reduce the code, but will try that tomorrow.