Report forwarded to debian-bugs-dist@lists.debian.org, Sven Rudolph <sr1@inf.tu-dresden.de>:
Bug#8298; Package lprng.
debian-bugs-dist@lists.debian.orgSven Rudolph
Subject: Bug#8298: LPRng doesn't print to older lpr printers
Reply-To: Richard Kaszeta , 8298@bugs.debian.org
Resent-From: Richard Kaszeta
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Sven Rudolph
Resent-Date: Tue, 25 Mar 1997 02:03:01 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: lprng
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by bugs@bugs.debian.org id=B.85925530327402
(code B ref -1); Tue, 25 Mar 1997 02:03:01 GMT
Date: Mon, 24 Mar 1997 20:01:35 -0600
Message-Id: <199703250201.UAA07295@bofh.me.umn.edu>
From: Richard Kaszeta
To: submit@bugs.debian.org
package: lprng
version: 3.2.1-1
Okay, all my printers are remote printers on lpr-based SunOS 4.1.3
machines.
Attempting to print to either these machines or a SGI running Irix 6.2
(running 'lp' set up to accept 'lpr' style print jobs) both yield
"malformed from address"
LPRng cannot print to them. The postinst mentions the that "bk" flag
is needed in /etc/printcap. Adding this flag has no effect on
printing behavior, the error is the same.
Further investigation shows the the "send_data_first" flag may be
needed as well. However, this flag also makes no difference. Indeed,
no combination of "bk" and "send_data_first" seems to allow me to
print.
FWIW, my recent attempts at building LPRng myself resulted in the same
thing.
Anyone have any enlightment?
--
Richard W Kaszeta Graduate Student/Sysadmin
bofh@bofh.me.umn.edu University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta
Acknowledgement sent to Richard Kaszeta <kaszeta@me.umn.edu>:
New bug report received and forwarded. Copy sent to Sven Rudolph <sr1@inf.tu-dresden.de>.
-t
From: owner@bugs.debian.org (Ian Jackson)
To: Richard Kaszeta
Subject: Bug#8298: Acknowledgement (was: LPRng doesn't print to older lpr printers)
Message-ID:
In-Reply-To: <199703250201.UAA07295@bofh.me.umn.edu>
References: <199703250201.UAA07295@bofh.me.umn.edu>
Thank you for the problem report you have sent regarding Debian Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Sven Rudolph
If you wish to submit further information on your problem, please send
it to 8298@bugs.debian.org (and *not* to
bugs@bugs.debian.org).
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at submit) by bugs.debian.org; 25 Mar 1997 02:01:43 +0000
Received: (qmail 27400 invoked from network); 25 Mar 1997 02:01:42 -0000
Received: from meserv.me.umn.edu (134.84.196.1)
by master.debian.org with SMTP; 25 Mar 1997 02:01:41 -0000
Received: from bofh.me.umn.edu (kaszeta@bofh.me.umn.edu [134.84.197.38]) by meserv.me.umn.edu (8.8.5/8.6.11) with ESMTP id UAA11302 for ; Mon, 24 Mar 1997 20:01:35 -0600 (CST)
Received: (from kaszeta@localhost)
by bofh.me.umn.edu (8.8.5/8.8.5) id UAA07295;
Mon, 24 Mar 1997 20:01:35 -0600
Date: Mon, 24 Mar 1997 20:01:35 -0600
Message-Id: <199703250201.UAA07295@bofh.me.umn.edu>
From: Richard Kaszeta
To: submit@bugs.debian.org
Subject: LPRng doesn't print to older lpr printers
package: lprng
version: 3.2.1-1
Okay, all my printers are remote printers on lpr-based SunOS 4.1.3
machines.
Attempting to print to either these machines or a SGI running Irix 6.2
(running 'lp' set up to accept 'lpr' style print jobs) both yield
"malformed from address"
LPRng cannot print to them. The postinst mentions the that "bk" flag
is needed in /etc/printcap. Adding this flag has no effect on
printing behavior, the error is the same.
Further investigation shows the the "send_data_first" flag may be
needed as well. However, this flag also makes no difference. Indeed,
no combination of "bk" and "send_data_first" seems to allow me to
print.
FWIW, my recent attempts at building LPRng myself resulted in the same
thing.
Anyone have any enlightment?
--
Richard W Kaszeta Graduate Student/Sysadmin
bofh@bofh.me.umn.edu University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta
Information forwarded to debian-bugs-dist@lists.debian.org, Sven Rudolph <sr1@inf.tu-dresden.de>:
Bug#8298; Package lprng.
debian-bugs-dist@lists.debian.orgSven Rudolph
Subject: Bug#8298: LPRng
Reply-To: Richard Kaszeta , 8298@bugs.debian.org
Resent-From: Richard Kaszeta
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Sven Rudolph
Resent-Date: Tue, 25 Mar 1997 17:03:04 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: lprng
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8298-bugs@bugs.debian.org id=B8298.85930906719476
(code B ref 8298); Tue, 25 Mar 1997 17:03:04 GMT
Date: Tue, 25 Mar 1997 10:57:39 -0600
Message-Id: <199703251657.KAA02813@bofh.me.umn.edu>
From: Richard Kaszeta
To: 8298@bugs.debian.org
Okay, I've isolated why lpr worked fine with my older lpd servers and
lpr does not.
The old lpr package installed lpr, lpq, etc as setuid. The lprng
package does not.
So either:
a. The clients should be installed setuid root so they can send
requests from a priveledged port.
b. Or the postinst should be modified to state that that if the remote
machine doesn't have LPRng the clients should be made setuid root in
addition to the :bk: flag which may or may not be needed.
--
Richard W Kaszeta Graduate Student/Sysadmin
bofh@bofh.me.umn.edu University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta
Acknowledgement sent to Richard Kaszeta <kaszeta@me.umn.edu>:
Extra info received and forwarded to list. Copy sent to Sven Rudolph <sr1@inf.tu-dresden.de>.
-t
From: owner@bugs.debian.org (Ian Jackson)
To: Richard Kaszeta
Subject: Bug#8298: Info received (was LPRng)
Message-ID:
In-Reply-To: <199703251657.KAA02813@bofh.me.umn.edu>
References: <199703251657.KAA02813@bofh.me.umn.edu>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
Sven Rudolph
If you wish to continue to submit further information on your problem,
please send it to 8298@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8298) by bugs.debian.org; 25 Mar 1997 16:57:47 +0000
Received: (qmail 19474 invoked from network); 25 Mar 1997 16:57:46 -0000
Received: from meserv.me.umn.edu (134.84.196.1)
by master.debian.org with SMTP; 25 Mar 1997 16:57:46 -0000
Received: from bofh.me.umn.edu (kaszeta@bofh.me.umn.edu [134.84.197.38]) by meserv.me.umn.edu (8.8.5/8.6.11) with ESMTP id KAA02832 for <8298@bugs.debian.org>; Tue, 25 Mar 1997 10:57:40 -0600 (CST)
Received: (from kaszeta@localhost)
by bofh.me.umn.edu (8.8.5/8.8.5) id KAA02813;
Tue, 25 Mar 1997 10:57:39 -0600
Date: Tue, 25 Mar 1997 10:57:39 -0600
Message-Id: <199703251657.KAA02813@bofh.me.umn.edu>
From: Richard Kaszeta
To: 8298@bugs.debian.org
Subject: LPRng
Okay, I've isolated why lpr worked fine with my older lpd servers and
lpr does not.
The old lpr package installed lpr, lpq, etc as setuid. The lprng
package does not.
So either:
a. The clients should be installed setuid root so they can send
requests from a priveledged port.
b. Or the postinst should be modified to state that that if the remote
machine doesn't have LPRng the clients should be made setuid root in
addition to the :bk: flag which may or may not be needed.
--
Richard W Kaszeta Graduate Student/Sysadmin
bofh@bofh.me.umn.edu University of MN, ME Dept
http://www.menet.umn.edu/~kaszeta
Information forwarded to debian-bugs-dist@lists.debian.org, Sven Rudolph <sr1@inf.tu-dresden.de>:
Bug#8298; Package lprng.
debian-bugs-dist@lists.debian.orgSven Rudolph
Subject: Bug#8298: Printing using lprng to old lpr printservers - a solution
Reply-To: Elad Tsur , 8298@bugs.debian.org
Resent-From: Elad Tsur
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Sven Rudolph
Resent-Date: Tue, 10 Jun 1997 20:33:03 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Message: report 8298
X-Debian-PR-Package: lprng
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8298-bugs@bugs.debian.org id=B8298.8659746728895
(code B ref 8298); Tue, 10 Jun 1997 20:33:03 GMT
Date: Tue, 10 Jun 1997 23:30:45 +0300 (IDT)
To: 8298@bugs.debian.org
From: Elad Tsur
Message-Id:
X-Mailer: TkMail 4.0beta8
The problem results from that that the lpr program of lprng access remote
servers directly, event if they are defined in /etc/printcap. However
by using the bq option, the files are first transferred to the local lpd,
wich then have no problem talking to older lpd's as it is running with
uid 0. So there is no need to suid lpr...
Here is an example printcap entry
(I've found that the bk option is not needed -YMMV):
ccps|lp|PostScript
:bq=ccps@server
:sd=/var/spool/lpd/lp
:if=/var/spool/lpd/lp/filter
Hope this helps...
--
Elad Tsur
Acknowledgement sent to Elad Tsur <eladts@ccsg.tau.ac.il>:
Extra info received and forwarded to list. Copy sent to Sven Rudolph <sr1@inf.tu-dresden.de>.
-t
From: owner@bugs.debian.org (Ian Jackson)
To: Elad Tsur
Subject: Bug#8298: Info received (was Printing using lprng to old lpr printservers - a solution)
Message-ID:
In-Reply-To:
References:
X-Debian-PR-Message: ack-info-maintonly 8298
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
Sven Rudolph
If you wish to continue to submit further information on your problem,
please send it to 8298@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8298) by bugs.debian.org; 10 Jun 1997 20:31:12 +0000
Received: (qmail 8891 invoked from network); 10 Jun 1997 20:31:04 -0000
Received: from post.tau.ac.il (132.66.16.11)
by master.debian.org with SMTP; 10 Jun 1997 20:31:00 -0000
Received: from tsur (root@ppp15-4.tau.ac.il [132.66.250.154])
by post.tau.ac.il (8.8.5/8.8.4) with ESMTP
id XAA04815 for <8298@bugs.debian.org>; Tue, 10 Jun 1997 23:26:30 +0300 (IDT)
Received: by tsur
id m0wbXYz-000NRUC
(Debian Smail-3.2 1996-Jul-4 #2); Tue, 10 Jun 1997 23:30:45 +0300 (IDT)
Date: Tue, 10 Jun 1997 23:30:45 +0300 (IDT)
Subject: Printing using lprng to old lpr printservers - a solution
To: 8298@bugs.debian.org
From: Elad Tsur
Message-Id:
X-Mailer: TkMail 4.0beta8
The problem results from that that the lpr program of lprng access remote
servers directly, event if they are defined in /etc/printcap. However
by using the bq option, the files are first transferred to the local lpd,
wich then have no problem talking to older lpd's as it is running with
uid 0. So there is no need to suid lpr...
Here is an example printcap entry
(I've found that the bk option is not needed -YMMV):
ccps|lp|PostScript
:bq=ccps@server
:sd=/var/spool/lpd/lp
:if=/var/spool/lpd/lp/filter
Hope this helps...
--
Elad Tsur