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


Groups > linux.debian.user > #257786

Re: repeat of previous question that has gone unanswered severaltimes.

From gene heskett <gheskett@shentel.net>
Newsgroups linux.debian.user
Subject Re: repeat of previous question that has gone unanswered severaltimes.
Date 2023-05-01 15:50 +0200
Message-ID <GqC4F-5OnQ-3@gated-at.bofh.it> (permalink)
References <Gqol3-5FqD-1@gated-at.bofh.it> <GqpqN-5G2p-5@gated-at.bofh.it> <GqwiB-5Kit-1@gated-at.bofh.it> <GqBii-5NSo-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 5/1/23 08:56, Brian wrote:
> On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote:
> 
>>>     avahi-browse -rt _ipp._tcp
>> gene@bpi51:~$ avahi-browse -rt _ipp._tcp
>> +   eth0 IPv4 Brother HL-L2320D series @ coyote             Internet Printer
>> local
>> +   eth0 IPv4 Brother MFC-J6920DW @ coyote                  Internet Printer
>> local
>> +   eth0 IPv4 HLL2320D @ coyote                             Internet Printer
>> local
>> +   eth0 IPv4 MFCJ6920DW _tray_2 @ coyote                   Internet Printer
>> local
> 
> You have exactly four (not five or six) print queues manually set up on
> the CUPS server coyote (192.168.71.3). It is assumed that when sat at
> coyote it is possible to print to any of Brother HL-L2320D series, Brother
> MFC-J6920DW, HLL2320D and  MFCJ6920DW _tray_2. Im particular - can you
> print to HLL2320D from the server?
> 
Yes, and from any buster machine on my local network.
> [...]
> 
>> =   eth0 IPv4 HLL2320D @ coyote                             Internet Printer
>> local
>>     hostname = [coyote.local]
>>     address = [192.168.71.3]
>>     port = [631]
>>     txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2"
>> "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
>> "product=(Brother HL-L2320D series)" "priority=0"
>> "adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother HL-L2320D
>> for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]
> 
> As well as three other printers, the host bpi51 sees the shared HLL2320D @ coyote
> queue via mDNS/DNS-SD. All is well and good up to now. Let's have
> 
>    lpstat -l -e
gene@bpi51:~$ lpstat -l -e
Brother_HL_L2320D_series_coyote network none 
ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups
Brother_MFC_J6920DW_coyote network none 
ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups
HLL2320D_coyote network none 
ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups
MFCJ6920DW_tray_2_coyote network none 
ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups
PDF permanent ipp://localhost/printers/PDF cups-pdf:/

>    lpstat -a
gene@bpi51:~$ lpstat -a
PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05

>    lpinfo -v
gene@bpi51:~$ lpinfo -v
-bash: lpinfo: command not found
gene@bpi51:~$ sudo apt install lpinfo
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package lpinfo

> 
> from bpi51.
> 
Thank you Brian

Take care and stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Back to linux.debian.user | Previous | NextPrevious 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