Bug 10277 - Problem with samba printing
Summary: Problem with samba printing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: samba
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-03-21 01:26 UTC by mal
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-03-27 16:18:44 UTC
Embargoed:


Attachments (Terms of Use)

Description mal 2000-03-21 01:26:34 UTC
I have a HPLJ4 printer connetcted to Linux.
This printer is configured with PS filter
via ghostcript and all programs print
PostScript to this printer.
Everything works fine when printing PostScript from Linux.
This printer is also shared via samba
to windows network.

The problem is:
when printing PostScript from Windows via samba
something does not recognize that this is PostScript
and I see just PostScript text printed.
GhostScript either not called or does not recognize that this is
PostScript.
In the same time when
I save PostScript output of windows program to a file tmp.ps
and then give
lpr tmp.ps
command on Linux the file is printed OK,
ghostscript successfully converts PS to HP printer PCL.

Comment 1 Nalin Dahyabhai 2000-03-21 12:50:59 UTC
Do you have "postscript = true" set in the relevant section of your
/etc/smb.conf configuration file?

Comment 2 mal 2000-03-23 20:14:59 UTC
I tried postscript=true option.
It works with it, but this option
requires one to put every printer to smb.conf
I can not just export all printers as it was before,
because postscript=true option screws up non-PostScript
printing when set globally.

In general case it may be better to configure
samba automatically set this option
if specific printer is known to be PostScript printer.

Comment 3 Bill Nottingham 2000-07-15 18:49:08 UTC
I'm closing this, as it seems to be more of a configuration issue
than a samba bug.


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