Hi,

We're using LPRng-3.8.26 and ifhp-3.5.17 on RHE 3.0 (both are compiled
from source so that we could run both cups and lprng.)  Everything works
well when jobs are submitted from localhost, including both samba and
cups submissions that print through lprng.  However, jobs submitted via
lpr/lp from external hosts (running both Tru64 and Solaris) stall
temporarily with the following information in status.pr:

hp: Set_hold_file: LOGIC ERROR- no HF_NAME in job information - [EMAIL PROTECTED]
cftransfername=cfmyclient.Colorado.EDU
D=2004-03-09-16:50:19.680
datafile_count=0
file_hostname=myclient.Colorado.EDU
H=myclient.Colorado.EDU
hold_time=0x0
job_time=0x404e583b
job_time_usec=0xa58bc
Q=hp
remotehost=myclient.Colorado.EDU
remoteport=0x3ff
size=0
unixsocket=0x0
update_time=2004-03-09-16:50:19.680 at 2004-03-09-16:50:19.680 ## A=<NULL> number=0 pro
cess=2555
waiting for subserver to exit at 2004-03-09-16:57:48.102 ## A=<NULL> number=0 process=2
572
subserver pid 2579 starting at 2004-03-09-16:57:48.102 ## [EMAIL PROTECTED] number
=834 process=2579

As you can see from the last line, eventually, the job does print
normally.   Any advice on the cause or fix of this temporary failure
would be greatly appreciated.

Thanks,
Mark

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

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