

I had no problem getting a shared printer to stick as a default.HTH,Bud
How to print in bash on mac mac#
Now, the printers served from the CUPS server will show up as shared printers on your Mac when you go to print. Then, you need to restart cupsd (accomplished by me by restarting my Mac in linux I would have just run the restart init script for cupsd). Where server.ip.address is either the DNS name of the CUPS server or its numeric IP and portNo is by default the number 631 (check with your server admin if that does not work). Edit your CUPS configuration file, found at /etc/cups/nf, adding the following line shortly after the line that begins # BrowsePoll:

Now, if you have a CUPS server that is not on your local subnet, there is a simpler way to print to the printers it serves than described by the hint. When the CUPS server is on a remote subnet, it is hard to get printing to the printers it serves to work from a Mac. Connections to CUPS servers on your local subnet do occur automatically.

Comments below that say "it just worked without any intervention from me" are clearly connecting to CUPS servers on their local subnet. If you find some way to select Raw from Apple's Printer Setup Utility, please post it in the comments.Ĭontrary to several comments below, there is a problem printing to printers served by CUPS servers that are not on your local subnet. This means you have to select it every time. Because we have to set up the printer in this manner, it will appear in our print settings as a 'Shared' printer and thus cannot be the default printer (if you know of a way to get it back into the list of local printers, please post in the comments). So what's the problem? We need to use the web interface to set this printer up because Apple (in their wisdom) have decided not to include Raw printing in their setup. Your printer is now set up and will be in the list of Shared Printers when you go to print.Select 'Raw Queue (en)' (or anything else if you have other languages) and Click Continue.If you created the printer with Apple's 'Printer Setup Utility', you'll need to change the /ipp/ to /printers/ at this point (Apple seem to be redefining standards. Check with your sysadmin if you're not sure. This will look like ipp://1.2.3.4/printers/queue_name, where 1.2.3.4 is the IP (or the address) of the print server. On the next screen select 'Internet Printing Protocol (ipp)' and press 'Continue'.The description will be in your Print settings when you print and it can contain spaces. If you have already created the printer, click 'Modify Printer'.

The name must only be made up of printable characters (A-Z, a-z, 0-9, _, no spaces!). Have you already created the printer? If not click the 'Add Printer' button and enter a name for the printer.This will give you a list of currently installed printers on your Mac. However Apple have not included every option. This is a front end to the printer admin, Apple's 'Printer Setup Utility' is just a front end to the same place. Make the printer on the mac into a 'raw' printer. The work-around is to make one end of the chain a 'raw' printer. The remote CUPS server will then try to render the already rendered file and will give a no_file error. It will then send the rendered file to the remote CUPS server. This is because Panther runs CUPS as its own print engine, and will attempt to render the PostScript for you once you select your correct printer driver. In Panther, it can be difficult to print to a remote CUPS server.
