go ahead... be a heretic | |
PerlMonks |
Hang on STDOUTby DanEllison (Scribe) |
on Jul 02, 2015 at 12:55 UTC ( [id://1132970]=perlquestion: print w/replies, xml ) | Need Help?? |
DanEllison has asked for the wisdom of the Perl Monks concerning the following question: I'm using Strawberry Perl in a Windows 8 environment. I have a scheduler I have written in Perl that I have been using for a couple of years. Its a threaded application that runs more than 1500 jobs every night, so its doing a lot of the same thing over and over. The main engine spawns worker threads to run the individual jobs and reports some progress to STDOUT. I have had issues in the past where STDOUT would somehow get corrupted and the engine would stop reporting progress but continue to run and I would eventually find my progress messages in one of the job log files. I haven't seen that issue in a while, but lately I find the engine has simply hung. It writes messages to both STDOUT and to a log file, and I've been adding debugging left and right, and it simply appears to be hanging on prints to STDOUT. Autoflush is on and I can see single character updates, but here's an example: $_[0] is the message I want to print. I thought maybe I was hanging trying to get the local time, but no. I put the < and > prints on either side of the localtime, but it hung between the > and the printf of the message. Has anyone had experience with this?
Back to
Seekers of Perl Wisdom
|
|