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

List:       kde-bugs-dist
Subject:    Bug#16312: CUPS client with Samba-lpd remote printer
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-11-30 18:09:54
[Download RAW message or body]

On Thursday 30 November 2000 17:45, Jean-Marie Gouarné wrote:
> 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...

What does this have to do with KDE ?

I think you should use the bug reporting system of your distribution.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://www.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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