Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 3533 - lpd problem with remote printing...
Summary: lpd problem with remote printing...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lpr
Version: 6.0
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-06-17 15:09 UTC by richarde
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-06-17 15:20:54 UTC


Attachments (Terms of Use)

Description richarde 1999-06-17 15:09:20 UTC
Upgraded print server from 5.2 to 6.0.  Following upgrade,
any job submitted remotely to the print server for a queue
with an input filter does not go through, and generates the
following errors in /var/log/messages:


Jun 16 14:18:29 redstart lpd[1196]: Can't create temp cfp
file
Jun 16 14:18:29 redstart last message repeated 1011 times
Jun 16 14:18:29 redstart lpd[1196]: lp: can't scan
/var/spool/lpd/lp

Removing the IF filter on the print server fixes the
problem.  This was confirmed to occur on a fresh 6.0
install, as well as an upgrade.  Local printing to the same
queue works properly with or without an IF filter.
Additionally, Samba printing will not produce output on ANY
queue, although connections can be made and are registered
normally in /var/log/samba/log.  There is simply no output.

Comment 1 Bill Nottingham 1999-06-17 15:20:59 UTC
1) the cfp problem should be fixed in lpr-0.36-4, available
from Raw Hide.
2) uncomment the 'printing = bsd' line in the smb.conf file...
(this was fixed in a later samba release)


Note You need to log in before you can comment on or make changes to this bug.