Talk:Cups: Difference between revisions

From Alpine Linux
(why a webserver?)
 
No edit summary
Line 1: Line 1:
Re: the "Webserver first" todo: Why is a webserver necessary?
Re: the "Webserver first" todo: Why is a webserver necessary?
-- [[User:Dubiousjim|Dubiousjim]] 16:04, 24 March 2012 (UTC)
-- [[User:Dubiousjim|Dubiousjim]] 16:04, 24 March 2012 (UTC)
Looks like this doesn't really apply to the current page, but I'd presume that a "webserver" for cups would refer to the admin page (http://localhost:631/admin).
As far as updating this to work, I can say the following:
* I used
Listen 192.168.2.*
...
Allow 192.168.2.*
instead of
Listen *:631
...
Allow from 192.168.2.0/24
* I had to run these commands manually after updating cupsd.conf and restarting cups:
cupsctl --share-printers
lpadmin -p Printer_Name -o printer-is-shared=true
* It is then necessary to point the clients at your new print server, via lpadmin or /etc/cups/client.conf
-- [[User:Idunham|Idunham]] 17:23, Oct 24 2015 (PDT)

Revision as of 00:25, 5 October 2015

Re: the "Webserver first" todo: Why is a webserver necessary? -- Dubiousjim 16:04, 24 March 2012 (UTC)

Looks like this doesn't really apply to the current page, but I'd presume that a "webserver" for cups would refer to the admin page (http://localhost:631/admin).

As far as updating this to work, I can say the following:

  • I used
Listen 192.168.2.*
...
Allow 192.168.2.*

instead of

Listen *:631
...
Allow from 192.168.2.0/24
  • I had to run these commands manually after updating cupsd.conf and restarting cups:
cupsctl --share-printers
lpadmin -p Printer_Name -o printer-is-shared=true
  • It is then necessary to point the clients at your new print server, via lpadmin or /etc/cups/client.conf

-- Idunham 17:23, Oct 24 2015 (PDT)