[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#16312: marked as done (CUPS client with Samba-lpd remote printer)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2000-11-30 18:03:09
[Download RAW message or body]

Your message dated Thu, 30 Nov 2000 18:49:55 +0100
with message-id <3A269343.4DF702F9@trolltech.com>
and subject line Bug#16312: CUPS client with Samba-lpd remote printer
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 30 Nov 2000 17:44:38 +0000
Received: (qmail 23249 invoked from network); 30 Nov 2000 17:44:37 -0000
Received: from unknown (HELO webmail.genicorp.fr) (213.11.11.253)
  by max.tat.physik.uni-tuebingen.de with SMTP; 30 Nov 2000 17:44:37 -0000
Received: from WS120.gennet.genicorp.fr (firewall1.genicorp.fr [192.168.0.1])
	by webmail.genicorp.fr (8.9.3/8.9.3) with SMTP id SAA07301
	for <submit@bugs.kde.org>; Thu, 30 Nov 2000 18:44:35 +0100
From: Jean-Marie =?iso-8859-1?q?Gouarn=E9?= <jm_g@genicorp.fr>
Reply-To: jm_g@genicorp.fr
Organization: GENICORP
Date: Thu, 30 Nov 2000 18:45:19 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="iso-8859-15"
To: submit@bugs.kde.org
Subject: CUPS client with Samba-lpd remote printer
MIME-Version: 1.0
Message-Id: <00113018451900.01353@WS120.gennet.genicorp.fr>
Content-Transfer-Encoding: 8bit

I'm not sure it's really a CUPS bug, but...

I'm working with a Linux workstation with CUPS and the Samba client.
My printer is in ordinary time attached to a Samba/Linux server. On the 
server side, there is a classic lpd system (not CUPS).

When I issue a "lpr filename" or "lp filename" from my station, all is OK.
But if I launch a "cat | lpr" without filename/jobname spec, the remote queue 
is blocked, and I get a message like : ""ERRDOS - Errfileexists (The file 
named in a Create Directory. Make new file or Link.    request already 
exists.) opening remote file (stdin)"

This problem desn't occur with a locally connected printer.
So, the lpr-cups command, when used with a pipe to stdin, without any 
filename nor explicit jobname, desn't allow the print server to create and 
execute a valid job.
As a result, while many applications use to print with a piped lp or lpr 
command without explicit jobname/filename, it's very difficult to print over 
a network.

I found only one (ugly) workaround : I've replaced the /usr/bin/lpr symbolic 
link to lpr-cups by my own lpr script, which calls lpr-cups with a forced "-J 
random_jobname" option. When an application pipes a flow to lpr, the really 
executed command is now : "cat | lpr-cups -J my_random_jobname"
In the same way, I've renamed the /usr/bin/lp binary as /usr/bin/lp2 and 
created my own  lp script which calls /usr/bin/lp2 with a "-t title" option.
So, my applications can print now. But it's a non-standard, non-elegant 
solution.

Is it a configuration error in my installation, a generic CUPS compatibility 
problem with samba-lpd servers, or a bug ?
I don't know. It's a question...

Thanks for your work. 

[prev in list] [next in list] [prev in thread] [next in thread]