Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #258140

Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.

From Brian <ad44@cityscape.co.uk>
Newsgroups linux.debian.user
Subject Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes.
Date 2023-05-11 21:20 +0200
Message-ID <GujZv-8crL-1@gated-at.bofh.it> (permalink)
References (5 earlier) <GtVDP-7Xda-1@gated-at.bofh.it> <GtWJz-7XP3-3@gated-at.bofh.it> <GtYil-7YY6-1@gated-at.bofh.it> <Guclj-87xI-7@gated-at.bofh.it> <Guh1D-8aCB-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

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.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
  Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
    Re: repeat of previous question that has gone unanswered several  times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
      Re: repeat of previous question that has gone unanswered several  times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
        Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
            Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
            Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
            Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
                Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
                Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
          Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
        Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
  Re: repeat of previous question that has gone unanswered several  times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
  Re: repeat of previous question that has gone unanswered several  times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
    Re: repeat of previous question that has gone unanswered several  times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
      Re: repeat of previous question that has gone unanswered several  times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
        Re: repeat of previous question that has gone unanswered several  times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
          Re: repeat of previous question that has gone unanswered  severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
            Re: repeat of previous question that has gone unanswered  severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
              Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
                Re: repeat of previous question that has gone  unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
                SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
                Re: SOLVED:Re: repeat of previous question that has gone  unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
                :Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
                Re: :Re: repeat of previous question  thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
                Re: SOLVED:Re: repeat of previous question that  hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
                Re: SOLVED:Re: repeat of previous question  thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
                Re: SOLVED:Re: repeat of previous  questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
                Re: SOLVED:Re: repeat of previous question that has  goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
                Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200

csiph-web