Re: [cups-devel] CUPS running on alternative port and alternative domain socket: Access via localhost restricted
Michael Sweet <[email protected]> Thu, 13 Oct 2016 09:36:53 -0400
| Newsgroups | gmane.comp.printing.cups.devel |
|---|---|
| Message-ID | <[email protected]> |
Till, > On Oct 12, 2016, at 8:37 PM, Till Kamppeter <[email protected]> wrote: >> ... >> Could you modify the trick from localhost:631 being replaced by the >> domain socket to localhost:<port on which current cupsd is running> >> being replaced by the domain socket? This way CUPS would be completely >> consistent. > > Now I have looked deeper into it and it seems that this cannot get changed, as the libcups cannot know which domain socket belongs to which CUPS daemon if there is more than one CUPS daemon 9AFAIK one cannot send a request to CUPS via localhost:port and get back the path of the domain socket, or is this possible?). There is currently no way to do this. I'm not sure that I'd want to add a way, either... _________________________________________________________ Michael Sweet, Senior Printing System Engineer