|
Simple smb.conf Settings for CUPS
To summarize,
the Simplest Printing-Related
smb.conf file shows the simplest printing-related setup for smb.conf to
enable basic CUPS support:
Example21.1.Simplest Printing-Related smb.conf
|
[global]
|
load printers = yes
|
printing = cups
|
printcap name = cups
|
|
[printers]
|
comment = All Printers
|
path = /var/spool/samba
|
browseable = no
|
public = yes
|
guest ok = yes
|
writable = no
|
printable = yes
|
printer admin = root, @ntadmins
|
This is all you need for basic printing setup for CUPS. It will print all graphic, text, PDF, and PostScript
files submitted from Windows clients. However, most of your Windows users would not know how to send these
kinds of files to print without opening a GUI application. Windows clients tend to have local printer drivers
installed, and the GUI application's print buttons start a printer driver. Your users also rarely send files
from the command line. Unlike UNIX clients, they rarely submit graphic, text, or PDF formatted files directly
to the spooler. They nearly exclusively print from GUI applications with a “printer driver”
hooked between the application's native format and the print data stream. If the backend printer is not a
PostScript device, the print data stream is “binary,” sensible only for the target printer. Read
on to learn what problem this may cause and how to avoid it.
|
|