Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #258158
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Date | 2023-05-12 12:30 +0200 |
| Message-ID | <Guyca-8ljm-13@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <Gumul-8dLC-1@gated-at.bofh.it> <GumXn-8eaM-1@gated-at.bofh.it> <GuocN-8ePR-1@gated-at.bofh.it> <GupVf-8fT9-1@gated-at.bofh.it> <Gux6p-8kH1-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 5/12/23 05:18, Vincent Lefevre wrote: > On 2023-05-11 21:34:11 -0400, gene heskett wrote: >> On 5/11/23 19:41, Vincent Lefevre wrote: >>> On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote: >>>> My questions would be: >>>> >>>> 1) Can you put *both* Listen lines in, to keep loopback working? >>> >>> The cupsd.conf(5) man page says: "Multiple Listen directives can be >>> provided to listen on multiple addresses." >>> >> My results seem to indicate otherwise. > > I don't think that you even showed anything. The only test you > should do about that is to try to connect to the port, e.g. with > telnet (or nmap can probably tell you). If the connection isn't > immediately refused, then the Listen directive is OK. > > For instance: > > zira:~> telnet localhost 631 > Trying ::1... > flushoutput character is 'off'. > Connected to localhost. > Escape character is '^]'. > > Fine. And you can try the same thing from a different machine on > the network, replacing "localhost" by the IP address of the server, > e.g. from another machine on my network: > > $ telnet 192.168.1.3 631 > Trying 192.168.1.3... > telnet: Unable to connect to remote host: Connection refused > I'm not able to test that on the bpi's, telnet is not installed. > because my CUPS server just has > > Listen localhost:631 > Listen /var/run/cups/cups.sock > > If the connection is accepted with telnet by using multiple Listen > directives, then the Listen configuration is correct. If you can > see any other issue related to the printers, then the problem is > due to something else. > 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 | Next — Previous in thread | Next in thread | Find similar | Unroll 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