I am not sure but I believe I sent this info but have not heard anything
back.
===============================================================
You asked in response to my question (see bottom of email);

This is usually the case with a filter process that does not exit.
There are several possibilities:

a)  The filter is waiting for status back that it never gets,
    and does not have a 'smart timeout' that will tell it to
    give up.

b)  The filter has done a 'close' on a socket but the socket does
    not close.  This is rare,  but happens when you have set 'sock_linger'
    to a long value OR the very bad 'wait forever' value.

c)  You have a hardware device that has a low level device driver that does
    not finish the close until it flushes its buffers.

>>What is the actual device?

 The device is an AXIS 540 IP to parallel print server. This particular
model is a single. The 560 is a multiple port and gave us our first problem
yesterday. More information on the printservers may be obtained from
www.axis.com

>>What is your printcap?
This is the entry for a multiport Axis 560

p-unddsp7|lp89:\                                
        :server:\                               
        :filter=/usr/local/libexec/filters/lpf:\
        :lf=/usr/adm/lp89err:\                  
        :lp=pr3@ps-udale11:\                    
        :sd=/usr/spool/lpd89:\                  
        :lpd_bounce                       

This is the entry for a Single Axis 540;

lp68|68|p-undrcv6:\
        :lp=:\
        :lf=/usr/adm/lp68err:\
        :rm=ps-udale5:\
        :rp=pr1:\
        :sd=/usr/spool/lpd68:      

>>What filter are you using?
  
We are not using any filter.

Any help or suggestion would be appreciated?
----------------snip-----------------------------------
>
> By killing the subprocess the jobs complete...
>
> root_# lpc status lp68
>  Printer           Printing Spooling Jobs  Server Subserver Redirect
> Status/(Debug)
> lp68@u-underdale3   enabled  enabled   17   27426   27425
> root_# kill -9 27425
>
> Leaving the process and resetting the printer and printserver does not
clear
> it up, but after killing the subprocess a new one starts and the printing
> resumes.
>
> Are there any known issues with this version for this type of lock up? Any
> other suggestions?
>
> Thanks 
> Wayne Blom 
> System Specialist 
> Technical Development Healthcare 
> F H Faulding & Co Limited 
> Ground Floor 
> 1 Station St 
> Hindmarsh SA 5007 
> Ph:         +61 8 8241 8334 
> FAX:      +61 8 8241 8357 
> Mobile:         +61 0419 808 496 
> Email:  [EMAIL PROTECTED] 


-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to