I am driving Suse 8.2, samba 2.2.7a, cups 1.1.18
As I mentioned recently I cannot see the cups printer queues from a
windows client even if lpq -Pprinter on the cups server gives the
correct status.
I tested a litte more and got the following results:
1.) If I configure samba to
printing = CUPS
printcap name = CUPS
I can see all queue entries in the windows status panel, too --
except for those jobs, that were sent by users with account names >= 8
characters. Is this a bug?
2.) If I configure samba to
printing = sysv
printcap name = CUPS
lpq command = lpstat -o %p
I can see the jobs only as they appear on the samba-/cups-server.
They disappear from the status panel immediatly when the spooling is
finished. Should it work? Anybody else has this problem?
--
Regards
Christoph Litauer
________________________________________________________________________
Christoph Litauer litauer@uni-koblenz.de
Uni Koblenz, Rechenzentrum, http://www.uni-koblenz.de/~litauer
Postfach 201602, 56016 Koblenz Fon: +49 261 287-1311, Fax: -100 1311
PGP-Key: http://www.uni-koblenz.de/~litauer/public-key.html
Christoph Litauer wrote:> I am driving Suse 8.2, samba 2.2.7a, cups 1.1.18 > > As I mentioned recently I cannot see the cups printer queues from a > windows client even if lpq -Pprinter on the cups server gives the > correct status. > I tested a litte more and got the following results: > > 1.) If I configure samba to > printing = CUPS > printcap name = CUPS > I can see all queue entries in the windows status panel, too -- > except for those jobs, that were sent by users with account names >= 8 > characters. Is this a bug? > > 2.) If I configure samba to > printing = sysv > printcap name = CUPS > lpq command = lpstat -o %p > I can see the jobs only as they appear on the samba-/cups-server. They > disappear from the status panel immediatly when the spooling is > finished. Should it work? Anybody else has this problem? >Another amazing thing is that I can use print command = my own command with parameters even if I configured printing = CUPS printcap name = CUPS My smbd is linked against cups: printhost:~ # ldd `which smbd` libacl.so.1 => /lib/libacl.so.1 (0x40026000) libcups.so.2 => /usr/lib/libcups.so.2 (0x4002d000) ... Here is what the documentation says: "With printing = cups, and if SAMBA is compiled against libcups, any manually set print command will be ignored." And yes I am shure "my own command" is executed I am a little bit confused ... what's happening here? -- Regards Christoph Litauer ________________________________________________________________________ Christoph Litauer litauer@uni-koblenz.de Uni Koblenz, Rechenzentrum, http://www.uni-koblenz.de/~litauer Postfach 201602, 56016 Koblenz Fon: +49 261 287-1311, Fax: -100 1311 PGP-Key: http://www.uni-koblenz.de/~litauer/public-key.html
Christoph Litauer litauer at uni-koblenz.de wrote on Samba-Digest:> Wed May 14 17:09:56 GMT 2003 > > > I am driving Suse 8.2, samba 2.2.7a, cups 1.1.18 > > As I mentioned recently I cannot see the cups printer queues from a > windows client even if lpq -Pprinter on the cups server gives the > correct status. > I tested a litte more and got the following results: > > 1.) If I configure samba to > printing = CUPS > printcap name = CUPS > I can see all queue entries in the windows status panel, too -- > except for those jobs, that were sent by users with account names >= 8 > characters.Interesting observation. How is the authentication setup of your system? I assume this is just a standalone Samba server? Or are you authenticating your Windows clients via a third source? Is the underlying Linux supporting user names longer than 8 chars? (Just to clarify: is it really also a problem with account names = 8 chars?)> Is this a bug?No idea.> 2.) If I configure samba to > printing = sysv > printcap name = CUPSShouldn't you use "printcap = /etc/printcap" ? (Probably smbd doesn't understand this setting anyway and therefore chooses the compiled-in default -- you could verify this by asking "testparm | grep printcap", "[ENTER]" twice...)> lpq command = lpstat -o %p > I can see the jobs only as they appear on the samba-/cups-server. > They disappear from the status panel immediatly when the spooling is > finished. Should it work?I guess it should... However.... CUPS knows both, the System V and the BSD variants of most print-related commands. And it returns the appropriate output formats to please legacy clients and systems. See this example: kde4@kde-bitshop:~> lpstat -o mopi mopi-1489 root 1024 Fri 03 Jan 2003 09:21:57 PM CET mopi-1490 root 1024 Fri 03 Jan 2003 09:22:31 PM CET mopi-1491 root 1024 Fri 03 Jan 2003 09:22:49 PM CET mopi-1492 root 1024 Fri 03 Jan 2003 09:22:57 PM CET mopi-1493 root 1024 Fri 03 Jan 2003 09:23:03 PM CET kde4@kde-bitshop:~> lpq -Pmopi mopi is ready Rank Owner Job File(s) Total Size 1st root 1489 motd 1024 bytes 2nd root 1490 motd 1024 bytes 3rd root 1491 motd 1024 bytes 4th root 1492 motd 1024 bytes 5th root 1493 motd 1024 bytes Check if you get a better result from the "lpq -P printername" variant....> Anybody else has this problem? > > -- > Regards > Christoph LitauerCheers, Kurt