On Jan 31, 2008 2:02 PM, RICHARD FERNANDEZ <[EMAIL PROTECTED]> wrote:
> Immediately before your test code I have a line that reads: > > print "Creating gzip'd archive\n"; > > and after the job runs, I definitely end up with a .gz file, just an > empty one. I was really hoping you were going to say, "and that line does show up in the output". So, you're saying that you have evidence that the new code is running, correct? Paul Johnson's point is a good one: "If you've just written the file, have you closed the filehandle and checked the return value?" If there are no warnings, but the code is running, it would seem that the file was created. Could you be clobbering it in some later code? That's where I'd look next. > I hate to do it, but I guess I'll have to shell out. If that fixes things, you've found a bug. But don't let me stop you; you can change it back just as easily once the bug is uncovered. Speaking of bugs, have you tried the debugger yet? Stop just before you try to gzip, and inspect the original file. Stop again just after, and inspect the result. (You don't even have to use the debugger to do this, but it makes it easier. Without a debugger, just copy the files so that you can look at the copies later.) If the result is not right, make a stand-alone program that replicates the original conditions, and you'll get the same result; file a bug report. Good luck with it! --Tom Phoenix Stonehenge Perl Training -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
