Conference kernel::unix_printing

    re .0
    
>    Mar  6 11:12:59 flamingo lpd[3242]: dt: Daemon filter 'f' terminated
>    (-1)
>    Mar  6 11:12:59 flamingo lpd[3242]: dt: filter/access error for
>    dfA000flamingo.m
>    Mar  6 11:12:59 flamingo lpd[489]: pid=3242 (sig=-1,err=0)
    
    If your print jobs are completing successfully, then the only real
    problem is that you're getting error messages that you shouldn't be.
    
    Changes for Asian printing that were introduced in 4.0 caused a status
    variable (inside lpd) to become stale, and falsely trigger an if-test
    or two that leads to these messages being printed out.  A fix for this
    was checked into the Steel development pool.  Though we haven't done so
    yet, we'll probably roll the fix into PTmin as well.
    
    	What I have discovered is that lpd is apparently having problems
    reading the cfa... file entry for:
    
>     f  Formatted File
>                Name of an already formatted file to print
>    	I can change the error message so that the first one "...Daemon filter
>    'f'..." changes to 'x' if I do lpr -x and the cfa... entry also changes
>    to 'x'.
>    	Additionally I have a Customer, of course, that is running
>    v4.0b/lpd sum of 32467 112, and he is experiencing the same symptom.
    
    What do you do to change the error message?
    
    But, again, if your jobs are completing fine, I suspect that you're
    only seeing the symptoms of the 'error' that was introduced as
    described above.
    
    -mark.

    Mark,
    	What I did to change the error message was to use the xf filter. 
    lpr -x -Pqueue /file-name would cause the Daemon filter error to have
    'x' instead of 'f' in it.  man lpd states:
    
      f  Formatted File
                Name of an already formatted file to print.
      x  Unfiltered output
                Do not interpret any control characters in the file.
    
    	which appears to be appropriate to the print command.
    
    	Another question same Customer.
    
    	The queue in question get data files from 3 different sources.
    o	# lpr
    o	Some application that pre-formats into PostScript
    o	PC running lpr protocol using HPLJ5 drivers that pre-format
    	into PJL code and then PostScript.
    
    	Is there one filter or one configuration that can handle data from
    all three sources?  The Customer has tried the hplaserxxxx
    filters with various results.  He would rather not have to use
    different print queues depending on the source.
    	It appears that if the data file has PJL code the filter assumes it
    has NOT been PS formatted and does it again causing garbage output.  If
    the data file is already PS formatted the PJL code is not added and the
    printer does not reset so that the next job prints on the back of the
    last page of the last job.
    	Any thoght anyone?
    
    David Matthies
    Open Systems Networking
    Customer Support Center

    Anyone have any thoughts on that last questions in .2?
           Another question same Customer.
    
            The queue in question get data files from 3 different sources.
        o   # lpr
        o   Some application that pre-formats into PostScript
        o   PC running lpr protocol using HPLJ5 drivers that pre-format
            into PJL code and then PostScript.
    
            Is there one filter or one configuration that can handle data
    from
        all three sources?  The Customer has tried the hplaserxxxx
        filters with various results.  He would rather not have to use
        different print queues depending on the source.
            It appears that if the data file has PJL code the filter
    assumes it
        has NOT been PS formatted and does it again causing garbage output. 
    If
        the data file is already PS formatted the PJL code is not added and
    the
        printer does not reset so that the next job prints on the back of
    the
        last page of the last job.
       
Thanks again,
    Dave,