Comment 8 for bug 288666

Revision history for this message
Stefan Lucke (stefan-lucke) wrote :

Still no one interested ! :-(((
I modified foomatic-rip-hplip like that (around line 3959):

            print $logh "---- start read write STDOUT\n";

            # The rest of the job data
     my $buf;
            while (read(KID4_IN, $buf, 1024)) {
                my $len = length ($buf);
                print $logh "---- read, try to write STDOUT ".$len."\n";
                print $fileh $buf;
                print $logh "---- written, retry to read STDOUT\n";
            }
            print $logh "---- stop read write STDOUT\n";

     # A JCL trailer
     if (( @jclprepend > 1 ) && (!$driverjcl)) {
  print $fileh @jclappend;
     }

            if (!close $fileh) {

and got the following logging information:
D [02/Oct/2009:19:22:09 +0200] [Job 541] ---- written, retry to read STDOUT
D [02/Oct/2009:19:22:09 +0200] [Job 541] ---- read, try to write STDOUT 1024
D [02/Oct/2009:19:22:09 +0200] [Job 541] ---- written, retry to read STDOUT
D [02/Oct/2009:19:22:09 +0200] [Job 541] ---- read, try to write STDOUT 1024
D [02/Oct/2009:19:22:43 +0200] Report: clients=0
D [02/Oct/2009:19:22:43 +0200] Report: jobs=278

So foomatic-rip-hplip is sitting at: print $fileh $buf;

Some out her with another idea ?