Bug 7935 – In lpr-0.46-1, lpd fails to pass the job name

Bug 7935 - In lpr-0.46-1, lpd fails to pass the job name

Summary:	In lpr-0.46-1, lpd fails to pass the job name

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lpr (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-12-21 14:01 EST by fossum
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-01-18 14:11:22 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description fossum 1999-12-21 14:01:17 EST

The latest version of lpd does not pass along the job name to the
remote printer.  Previous versions used the filename being printed
as the job name, so that

	lpr -Premote-printer somefile

would pass "somefile" as the job name to the remote printer.  This
no longer works.  Even using the -J switch on the lpr line does not
pass along a job name to the remote printer.  Other job-related info
(the Classification and Literal values) seem to be sent properly.

Comment 1 fossum 1999-12-24 15:18:59 EST

Added 24 December:

lpd does seem to propagate the filename on the 'N...' line in the control
file on the remote system, but not the 'J...' line.  What exactly is the
standard behavior?

Comment 2 fossum 1999-12-24 15:20:59 EST

Added 24 December:

lpd does seem to propagate the filename on the 'N...' line in the control
file on the remote system, but not the 'J...' line.  What exactly is the
standard behavior?

Comment 3 Bernhard Rosenkraenzer 2000-01-18 14:11:59 EST

0.50 should fix this

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