Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.
On Thu 11 May 2023 at 12:08:01 -0400, gene heskett wrote:
> On 5/11/23 07:07, Brian wrote:
> > On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote:
> >
> > > On 5/10/23 14:22, Brian wrote:
> > > > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
> > > >
> > > > > On 5/10/23 11:29, Brian wrote:
> > > > > > On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
> > > > > >
> > > > > > > On 5/10/23 08:17, Brian wrote:
> > > > >
> > > > > > [...]
> > > >
> > > > > > Is /etc/cups/client,conf really, really needed?
> > > > > >
> > > > > That is the first thing cups docs tell you to do, see "printer sharing"
> > > >
> > > > A link would be ever so useful.
> > >
> > > send browser to cups.org, click help, in right pane, click "printer
> > > sharing", scroll down about a screenfull to Automatic using IPP
> >
> > Thanks to you and debian-user@howorth.org.uk. Note that this page is for Apple
> > CUPS. The one for Debian CUPS is at
> >
> > https://openprinting.github.io/cups/doc/sharing.html
> >
> Thank you for that link, the other Apple Cups link is first in a google
> search, and probably close in DDG too since the search was for cups, not
> openprinting as I was not then aware that Mike had moved. Apple should be
> ashamed of themselves hanging onto the cups links when they are no longer
> writing the authors paychecks.
>
> > Havong said that, it should also be noted that the /etc/cups/client.conf is used
> > when a local spooler is not required and is presented as to be used only as
> > absolutely necessary. Hardly "the first thing cups docs tell you to do". Why is
> > it absolutely necessary in your situation?
> >
> > Additionally, a client.conf overrides the default local server. All the analysis
> > in this thread has been carried out assuming a functional local server, so I do
> > not know where that leaves us now if a client.conf has been in the mix all the time..
> >
> I am wondering now if I shouldn't remove the other Listen directives from
> cupsd.conf, isolating their influence when there are no locally connected
> printers.
>
> Aha!!!! Got it, geany evince okular etc can now print from bpi54! Removing
> the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
>
> Listen 192.168.xx.yy:631
>
> made the localhost:631/printers on this machine show up in FF on bpi54, all
> 5 choices from this machine. All that as root of course, and the acid test
> was me as 1st user, calling up geany to edit that file, which complained it
> was not writable but to print it on the B&W laser, which it just did. I did
> have to leave active the "Listen /run/cups/cups.sock" line, it did not work
> w/o that.
>
> I changed the LogLevel back to warn before it fills up a 64BG card, and it
> seems its all Just Working.
>
> That warning in the paragraph above s/not be a show stopper when there is
> only one machine as the Server on this local network. IMO, it should be
> speced as applying to any machine that does NOT have any locally connected
> printers.
>
> Your help, and some comments from Greg, have been very helpful. Thank you
> both for bearing with me, most appreciated.
You are, as uaual, treading your own path. Sometimes, it touches on mine
or crosses it. Let's leave it there. The acknowledgement is gracious and
appreciated.
--
Brian.
Reply to: