Hi,sorry to jump in there - I've curiously waited for an answer on Elmars question.
I've seen these interrupts too. But unfortunately I haven't found any critieria to reproduce it (our application does just one print and people using it just tell me that it "happened" again (they can glue the two pieces together by a text editor) - but too late to reproduce it). Size doesn't seem to matter at all.
For the command I use something likeoutputcommand=/bin/cat > /tmp/as400.printout.txt; /usr/local/bin/as400printout.sh print /tmp/as400.printout.txt
printout.sh does some streamlining of the output. No big deal. But the "outputcommand" is definitely called twice (probably more - but never occurred here).
Regards, uwe James Rich wrote:
On Tue, 6 Dec 2005, elmars.ositis@xxxxxx wrote:(sorry to be slow in responding, I've been consumed in work these last few days)Recently we have started using lp5250d to output as400 spool files to text, which we then process for use in another manner. Since the Linuxprocess does not know whent the complete spool file has been received, itchecks the end of the file for specific content. If the content exists(*** END OF REPORT ***) then it assumes the document has been spooled andis ready for further processing.Are you saying that you modified lp5250d? lp5250d certainly does know when the end of the spool file has been reached. What makes you believe that it doesn't? The following outputcommand works perfectly for me:outputcommand = scs2pdf> /home/samba/STSE09-`date +%Y-%m-%d-%H-%M-%S`.pdf James Rich It's not the software that's free; it's you. - billyskank on Groklaw