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

Groups > alt.os.linux.slackware > #34052 > unrolled thread

Networking problem trying to set up CUPS

Back to article view | Back to alt.os.linux.slackware

Contents

  Networking problem trying to set up CUPS Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-02-20 19:29 -0400
    Re: Networking problem trying to set up CUPS Rich <rich@example.invalid> - 2023-02-21 02:55 +0000
      Re: Networking problem trying to set up CUPS Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2023-02-22 12:32 +1100
        Re: Networking problem trying to set up CUPS Rich <rich@example.invalid> - 2023-02-22 13:28 +0000
    Re: Networking problem trying to set up CUPS Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-02-21 06:34 +0000
      Ping Henrik Re: Networking problem trying to set up CUPS Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-03-05 19:14 -0400
        Re: Ping Henrik Re: Networking problem trying to set up CUPS Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-06 06:54 +0000
          Tnx Re: Ping Henrik Re: Networking problem trying to set up CUPS Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-03-08 01:25 -0400
            Re: Tnx Re: Ping Henrik Re: Networking problem trying to set up CUPS Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-08 20:48 +0000
              Latex Re: Tnx Re: Ping Henrik Re: Networking problem... Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-03-11 03:24 -0400
                Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem... Martin Schöön <martin.schoon@gmail.com> - 2023-03-11 09:25 +0000
                Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem... Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-11 10:13 +0000
                  Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem... maus <maus@mail.com> - 2023-03-11 11:30 +0000
                    Re: Latex Javier <invalid@invalid.invalid> - 2023-03-12 03:52 +0000
                      Re: Latex maus <maus@mail.com> - 2023-03-12 08:59 +0000
                      Re: Latex Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-12 11:04 +0000
                        Re: Latex Javier <invalid@invalid.invalid> - 2023-03-12 17:10 +0000
                          Re: Latex Javier <invalid@invalid.invalid> - 2023-03-12 17:48 +0000
                          Re: Latex Martin Schöön <martin.schoon@gmail.com> - 2023-03-12 20:42 +0000
                            Re: Latex Javier <invalid@invalid.invalid> - 2023-03-12 21:17 +0000
                              Re: Latex Martin Schöön <martin.schoon@gmail.com> - 2023-03-13 20:08 +0000
                        Re: Latex Jim Diamond <JimDiamond@ns.sympatico.ca> - 2023-03-13 21:14 -0300
                          Re: Latex Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2023-03-15 06:26 +0000
                            Re: Latex Jim Diamond <JimDiamond@jdvb.ca> - 2023-03-20 16:05 -0300
                      Re: Latex Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-03-13 00:54 -0300
                Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem... Eric Pozharski <whynot@pozharski.name> - 2023-03-11 14:27 +0000
                Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem... Jim Diamond <JimDiamond@ns.sympatico.ca> - 2023-03-13 21:21 -0300
    Re: Networking problem trying to set up CUPS John Forkosh <forkosh@panix.com> - 2023-02-21 07:56 +0000
    Re: Networking problem trying to set up CUPS Marco Moock <mo01@posteo.de> - 2023-02-21 14:47 +0100
      Re: Networking problem trying to set up CUPS Javier <invalid@invalid.invalid> - 2023-02-21 21:29 +0000
        Sendmaail (WAS: Re: Networking problem trying to set up CUPS) Mike Spencer <mds@bogus.nodomain.nowhere> - 2023-02-21 19:50 -0400
          Re: Sendmaail (WAS: Re: Networking problem trying to set up CUPS) Grant Taylor <gtaylor@tnetconsulting.net> - 2023-02-21 21:27 -0700
    Re: Networking problem trying to set up CUPS Javier <invalid@invalid.invalid> - 2023-02-21 21:19 +0000
    Re: Networking problem trying to set up CUPS Giovanni <lsodgf0@home.net.it> - 2023-02-22 12:59 +0100
    Re: Networking problem trying to set up CUPS Peter 'Shaggy' Haywood <phaywood@alphalink.com.au> - 2023-02-22 13:00 +1100

Page 2 of 2 — ← Prev page 1 [2]

#34146 — Re: Latex

Den 2023-03-12 skrev Javier <invalid@invalid.invalid>:
> Martin Schöön <martin.schoon@gmail.com> wrote:
>>> Not all of them where done on graphical office applications.  Kernighan's books
>>> are typeset with pic|tbl|eqn|troff -ms (as stated in page iv of K&R).
>>>
>> I guess he had to given his role in early UNIX development :-)
>
> They had to justify their funding to AT&T management :-)
>
>     https://nakamotoinstitute.org/static/docs/taoup.pdf
>
>     Unix's first real job, in 1971, was to support what would now be called
>     word processing for the Bell Labs patent department; the first Unix
>     application was the ancestor of the nroff(1) text formatter.  This
>     project justified the purchase of a PDP-11, a much more capable
>     minicomputer. Management remained blissfully unaware that the
>     word-processing system that Thompson and colleagues were building was
>     incubating an operating system. Operating systems were not in the Bell
>     Labs plan - AT&T had joined the Multics consortium precisely to avoid
>     doing an operating system on its own.

Thanks for the PDF. It is created by pdfTeX14.h so right on topic :-)

Kernighan himself on Computerphile:
https://www.youtube.com/watch?v=QFK6RG47bww&list=PLzH6n4zXuckqZ90zLyy36qjO5YIn1RulG

/Martin

[toc] | [prev] | [next] | [standalone]

#34148 — Re: Latex

On 2023-03-12 at 08:04 ADT, Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> On Sun, 12 Mar 2023 03:52:06 +0000, Javier wrote:
>> In fact, TeX is not very popular among UNIX programmers, and software
>> documentation is seldom written in LaTeX (with the exception of people
>> doing maths and physics).

> This is true, if you are only writing some programming documentation like 
> some design description or a requirement specification most people will 
> find it easier and more efficient to use som graphical office application 
> like LibreOffice or MS Word.

That presumes they know one of those; not everyone who does software
development was indoctrinated into the M$ tool space.  I've seen people use
all sorts of tools to produce documentation.  (Sometimes even just ordinary
plain text!)

                                Jim

[toc] | [prev] | [next] | [standalone]

#34164 — Re: Latex

On Mon, 13 Mar 2023 21:14:19 -0300, Jim Diamond wrote:

> On 2023-03-12 at 08:04 ADT, Henrik Carlqvist
> <Henrik.Carlqvist@deadspam.com> wrote:
>> This is true, if you are only writing some programming documentation
>> like some design description or a requirement specification most people
>> will find it easier and more efficient to use som graphical office
>> application like LibreOffice or MS Word.
> 
> That presumes they know one of those; not everyone who does software
> development was indoctrinated into the M$ tool space.  I've seen people
> use all sorts of tools to produce documentation.  (Sometimes even just
> ordinary plain text!)

Yes, but the learning curve will not be as steep for a graphical office 
application as for Latex. However, once you learn Latex you can use the 
same favorite editor for your documentation as you use for programming.

regards Henrik

[toc] | [prev] | [next] | [standalone]

#34186 — Re: Latex

On 2023-03-15 at 03:26 ADT, Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> On Mon, 13 Mar 2023 21:14:19 -0300, Jim Diamond wrote:
>
>> On 2023-03-12 at 08:04 ADT, Henrik Carlqvist
>> <Henrik.Carlqvist@deadspam.com> wrote:
>>> This is true, if you are only writing some programming documentation
>>> like some design description or a requirement specification most people
>>> will find it easier and more efficient to use som graphical office
>>> application like LibreOffice or MS Word.

>> That presumes they know one of those; not everyone who does software
>> development was indoctrinated into the M$ tool space.  I've seen people
>> use all sorts of tools to produce documentation.  (Sometimes even just
>> ordinary plain text!)

> Yes, but the learning curve will not be as steep for a graphical office 
> application as for Latex.

I think that is true to a point.  A brand new can bang out a word-processor
document with little help.  However, if one wants to learn the "advanced"
features of word processors there will be a non-trivial learning curve
there as well.  But it seems a lot of people (that I've seen) never get
much beyond the beginner stage with word processors, and maybe this
(alleged at least by me) learning curve is the reason for it.

Having said that, you can bang out a simple document in plain TeX if you
just know enough to put "\bye" or "\end" at the end.  (And you need to know
how to use some text editor, of course.)

> However, once you learn Latex you can use the same favorite editor for
> your documentation as you use for programming.

I agree whole-heartedly.  The "editor" in word-processors is one of the
things I really detest about them.

I've never used Lyx, but I wonder how someone who knows nothing about
either word processors or LaTeX, given Lyx, would compare to someone who is
given a word processor to use.

In any case, I still think that the current state of LaTeX is a botch.
Perhaps when LaTeX 3 comes out it won't be such a mess.

                                Jim

[toc] | [prev] | [next] | [standalone]

#34142 — Re: Latex

Javier <invalid@invalid.invalid> writes:

> maus <maus@mail.com> wrote:
>
>> Lamport's book on latex is all you will ever need.

Tnx for the pointer, saved for reference, but see below.

> [snip]
> latexmk makes compiling documents much nicer....
> [snip]
> Another thing that will piss off somebody from the UNIX world is how
> poor the manpage documentation is.  There is an info manual.
> It does document the language quite well, but does not say much about
> the CLI tools.  In emacs you should see it with
> 
> M-: (info "(latex2e) Top")

Gak!

> I began using both LaTeX and UNIX almost at the same time, so I was
> not really questioning the design of TeX when I was learning, but the
> OP...

That would be me.

> ...who has been using UNIX for decades, will be shocked by the design
> of the TeX tools.
> 
> For the OP, I would think twice before diving into LaTeX.  It has many
> pitfalls, error reporting is not always clear and takes long time to learn.
> If the OP has a simpler way of writing letters, I would put LaTeX aside.

This is probably the course I'll follow.  "Never say never..." but I
have way too many other things to do, most of them more useful and
more interesting, to undertake beating up Latex without a compelling
motive. 

Tnx,
-- 
Mike Spencer                  Nova Scotia, Canada

[toc] | [prev] | [next] | [standalone]

#34129 — Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem...

with <87h6urbvjc.fsf_-_@bogus.nodomain.nowhere> Mike Spencer wrote:
> Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> writes:
>> On Wed, 08 Mar 2023 01:25:46 -0400, Mike Spencer wrote:

>>> I don't have a word processor.  On the very rare occasions that I
>>> need to print a business letter, I compose it in simple HTML and
>>> print from the browser.
>> HTML might work, but if you want really nice letters you should learn
>> latex!
*SKIP*
> But when I went to my shiny new Linux system a few years later, it had
> Latex or Tetex or something that was a dialect of TEX.

(disclaimer: I'm not that immersed).  It's called 'texlive' now.
(caveat:) proper capitalization might be an issue;  however I've not
seen fights about it ;)

*SKIP*
> Is there an online tutorial PDF for Latex that's simple-minded?  I'm
> never going to compose a glossy magazine page, advanced scientific
> paper or legal brief and my ageing brain isn't going to master a mass
> of arcana to be used, say, once a quarter.

'lshort.pdf' really got me going back then.  Never looked back.

*CUT*

-- 
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom

[toc] | [prev] | [next] | [standalone]

#34149 — Re: Latex Re: Tnx Re: Ping Henrik Re: Networking problem...

On 2023-03-11 at 03:24 AST, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>
> Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> writes:
>
>> On Wed, 08 Mar 2023 01:25:46 -0400, Mike Spencer wrote:
>>
>>> I don't have a word processor.  On the very rare occasions that I
>>> need to print a business letter, I compose it in simple HTML and print
>>> from the browser.
>> 
>> HTML might work, but if you want really nice letters you should learn 
>> latex!
>
> But when I went to my shiny new Linux system a few years later, it had
> Latex or Tetex or something that was a dialect of TEX.  I bumbled
> about a bit but never found a tutorial that was simple enough to just,
> yew kno, bang out a nice page.  All seemed too much like learning a
> new programming language (yeah, I know what a macro is but...)  to
> become a pro compositor.

I find LaTeX to be the ultimate poorly-designed system.  It attempts to be
all things to all people, and then falls over its own feet trying to do
that.  Because of all the "helpful" packages people have contributed over
time, situations where package A conflicts with package B show up with
disturbing regularity.

(plain) TeX gets a lot of hate from LaTeX people, but if all you want to do
is to bang out a nice page, you may find plain TeX easier to use.  By
itself it is pretty low-level, and without writing your own macros you
would end up explicitly changing fonts, explicitly specifying when text is
to be centered, and so on.  But if you accept that, the learning curve is
pretty short.  If this is of any interest to you, feel free to contact me
directly (that's my real email addr above!) and I might be able to get you
going with plain TeX very quickly.  For, at least, banging out one-page
documents.

Cheers.
                                Jim

[toc] | [prev] | [next] | [standalone]

#34055

Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
> Now venturing to migrate from lprng to CUPS.
> Before I've even read how to start, there seems to be something I
> don't understand about inetd and  LAN networking.
> Cups man page says:
>    WHERE DO I BEGIN?
>        The easiest way to start is by using the web interface to
>        configure your printer. Go to "http://localhost:631" and choose
>        the Administration tab at the top of the page.
> Okay, but I want to access that (on enoch, the new 15 install box)
> from bogus, my current 14.2 main machine.  Try http://enoch:631.
>    The connection was refused when attempting to contact enoch:631
> I haven't started ip_tables yet so no firewall.
> cupsd is running:
>     enoch% pgrep cupsd
>     1055
> I've tried changing /etc/cups/cupsd.conf and /etc/inetd.conf in
> various ways (and restarting inetd or cupsd after any change) with no
> improvements.
> cupsd.conf:
>    # Only listen for connections from the local machine.
>    Listen localhost:631
>    Listen /var/run/cups/cups.sock
>    # mds -- Also listen for conns from bogus; 
>      Listen 192.168.0.15:631
> Using any of ip address (above), hostname (bogus) or *  gives same
> non-result.  Moreover, the cupsd.conf directive to listen doesn't show
> up in lsof:
> enoch-root$ lsof -i:631 -sTCP:LISTEN
> COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
> cupsd   1055 root    5u  IPv6  32275      0t0  TCP localhost:ipp (LISTEN)
> cupsd   1055 root    6u  IPv4  32276      0t0  TCP localhost:ipp (LISTEN)
> What about inetd?  Adding to /etc/inetd.conf a line like:
>   ipp  stream  tcp  nowait  root   /usr/sbin/tcpd  /usr/sbin/cupsd
> doesn't make any difference.
> It seems I'm trying to do something that can't be done.  Or that needs
> a magic incantation I don't know about.  Can I access cupsd:631 on
> enoch from bogus over the LAN?  Or not?
> TIA for any help.

Can't offer any explicit advice, but what kind of printer do you have???
I have several Brother printer models, and the brother homepage has
linux install scripts for all of them that work flawlessly with cups.
Just make sure /etc/rc.d/rc.cups has start'ed, turn on your printer
and make sure it's connected (presumably by wifi nowadays), and then
run the script. The necessary /etc/cups/, /usr/share/cups/, etc gets
automatically edited as needed, and the printers "just work" afterwards.
Not sure what similar linux install scripts other printer manufacturers
provide. But I'd suggest googling around for that first.
-- 
John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )

[toc] | [prev] | [next] | [standalone]

#34056

Am 20.02.2023 schrieb Mike Spencer <mds@bogus.nodomain.nowhere>:

> I gave up on postfix and reverted with complete success to sendmail.

:-)

> cupsd.conf:
> 
>    # Only listen for connections from the local machine.
>    Listen localhost:631
>    Listen /var/run/cups/cups.sock
> 
>    # mds -- Also listen for conns from bogus; 
>      Listen 192.168.0.15:631
> 
> 
> Using any of ip address (above), hostname (bogus) or *  gives same
> non-result.  Moreover, the cupsd.conf directive to listen doesn't show
> up in lsof:
> 
> enoch-root$ lsof -i:631 -sTCP:LISTEN
> 
> COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
> cupsd   1055 root    5u  IPv6  32275      0t0  TCP localhost:ipp
> (LISTEN) cupsd   1055 root    6u  IPv4  32276      0t0  TCP
> localhost:ipp (LISTEN)
> 
> What about inetd?  Adding to /etc/inetd.conf a line like:
> 
>   ipp  stream  tcp  nowait  root   /usr/sbin/tcpd  /usr/sbin/cupsd
> 
> doesn't make any difference.

Use either cups itself OR inetd - not both at the same time.

I recommend using CUPS directly if possible.
Please configure and restart the service and run "ss -lutn"

[toc] | [prev] | [next] | [standalone]

#34058

Marco Moock <mo01@posteo.de> wrote:
> Am 20.02.2023 schrieb Mike Spencer <mds@bogus.nodomain.nowhere>:
> 
>> I gave up on postfix and reverted with complete success to sendmail.
> 
> :-)

I wonder whether the OP wants to run a mail server himself or he
relies on an external SMTP server.  Running an mailserver nowadays is
not so easy nowadays, as many mailservers (especially those controlled
by MS like Yahoo or corporate Exchange servers) will drop the received
messages without warning for the silliest reason.

If he relies on an external SMTP server an userland based solution like
ssmtp should be easier

[toc] | [prev] | [next] | [standalone]

#34059 — Sendmaail (WAS: Re: Networking problem trying to set up CUPS)

Javier <invalid@invalid.invalid> writes:

> Marco Moock <mo01@posteo.de> wrote:
>
> > Am 20.02.2023 schrieb Mike Spencer <mds@bogus.nodomain.nowhere>:
>> 
>>> I gave up on postfix and reverted with complete success to sendmail.
>> 
>> :-)
> 
> I wonder whether the OP wants to run a mail server himself or he
> relies on an external SMTP server.  Running an mailserver nowadays is
> not so easy nowadays, as many mailservers (especially those controlled
> by MS like Yahoo or corporate Exchange servers) will drop the received
> messages without warning for the silliest reason.

No, no, I don't want to run a mail server.

Just nattering, for the record, if anyone is interested...

I only need three things from sendmail:

   1. Hand outgoing mail to a smarthost that requires AUTH (the
      deafult) 

   2. Occasionally hand outgoing mail to a different smarthost that
      doesn't require AUTH.

   3. Deliver mail from the kernel to root to a mailbox on localhost.

I get 1. & 2. by having 2 sets of files for /etc/mail/*, one
configured for 1., the other configured for 2.  If the the server for
1. is down, I can swap those files and restart sendmail.

3. seems to happen automatically without my having to do anything.

Setting up smarthosting, long ago, was so easy that I just manually
edited sendmail.cf before I knew you weren't supposed to do that.
Enabling AUTH was harder but I had earlier invested in the great, fat
O'Reilly Bat Book and could figure it out, use m4.

So sendmail is a Winnebago with all the dealer options, a Zodiac on
the roof, dirt bike strapped to the back and a 2-door Hyundai in tow.
And the config is written in cuneiform that you need a Rosetta stone
(m4) to deal with it.

Postfix is supposed to be better and easier.  My take is that it's
also A Winnebago, but without the dealer options or Zodiac.  To
stretch the metaphor, the config is written in Chaucerian English so
you only need hours of study, not a Rosetta stone,  to sort out and
disable all the details and features meant for a full-on SMTP server
and get just the simple behavior above.

Worse, documentation is in numerous files.  And there's no Bat Book.

> If he relies on an external SMTP server an userland based solution like
> ssmtp should be easier

Maybe.  More bother?  Sendmail is doing what I want in 15.0.

(Back to my problem with CUPS later, in another post.)

-- 
Mike Spencer                  Nova Scotia, Canada

[toc] | [prev] | [next] | [standalone]

#34060 — Re: Sendmaail (WAS: Re: Networking problem trying to set up CUPS)

On 2/21/23 4:50 PM, Mike Spencer wrote:
> 1. Hand outgoing mail to a smarthost that requires AUTH (the deafult)

This may become more of a problem as more and more providers are 
disabling traditional authentication methods, including SMTP Auth that 
you're talking about, in favor of OAUTH.

I'm not aware of any MTA supporting this on smart hosts.  Perhaps they 
do and I'm just ignorant of it.



-- 
Grant. . . .
unix || die

[toc] | [prev] | [next] | [standalone]

#34057

Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
> cupsd.conf:
> 
>    # Only listen for connections from the local machine.
>    Listen localhost:631
>    Listen /var/run/cups/cups.sock
> 
>    # mds -- Also listen for conns from bogus; 
>      Listen 192.168.0.15:631
> 
> 
> Using any of ip address (above), hostname (bogus) or *  gives same
> non-result.  Moreover, the cupsd.conf directive to listen doesn't show
> up in lsof:
> 

man cupsd.conf

From cupsd.conf(5):

            The Listen directive is similar to the Port directive but
            allows you to restrict access to specific interfaces or networks.

So I would use the Port directive instead, and delete all the Listen directives.

            Port 631

[toc] | [prev] | [next] | [standalone]

#34061

On 2/21/23 00:29, Mike Spencer wrote:

> It seems I'm trying to do something that can't be done.  Or that needs
> a magic incantation I don't know about.  Can I access cupsd:631 on
> enoch from bogus over the LAN?  Or not?
> 

Yes, you can, although if you do not have a browser that runs on enoch 
it may be a nightmare.

Best way is to start http://localhost:631 on enoch and follow the 
instructions to configure the printer leaving as required step to check 
'Allow remote administration' and 'Share printers connected to this 
system' on the main 'Administration' page.  After that the printer will 
be 'http://enoch:631/' from any machine on LAN.

I have a server without X services (it does non even have a display, 
only ssh access).  With older versions of cups I could use lynx but now 
cups uses java scripts and the only method is the command line interface 
and a few tweaks to the configuration file to insert the the server name.

If you cannot use a browser you need to use same method using command 
line interface.  Involved are 'lpadmin' and 'lpoptions' and their 
options. Remember that encryption does not work in latest version (at 
least on my machines).

##  Create default printer
lpadmin -p ml1210 -v "http://milena.home.net.it:631/printers/raw" -D 
"Samsung ML-1210 Laser Printer" -L "Local at MONICA" -P 
"/etc/cups/Samsung-ML-1210-gdi.ppd"
lpadmin -p ml1210 -o printer-is-shared=false
lpadmin -d ml1210

##  Set as user default
lpoptions -d ml1210
lpoptions -p ml1210 -o media=A4

This is an example to create a printer 'ml1210' that prints to a remote 
queue 'raw' a pass-thru queue accessible from LAN.  You have to modify 
the arguments to your needs

Ciao
Giovanni
-- 
   A computer is like an air conditioner,
   it stops working when you open Windows.
   < https://giovanni.homelinux.net/ >

[toc] | [prev] | [next] | [standalone]

#34062

Groovy hepcat Mike Spencer was jivin' in alt.os.linux.slackware on Tue,
21 Feb 2023 10:29 am. It's a cool scene! Dig it.

> Cups man page says:
> 
>    WHERE DO I BEGIN?
> 
>        The easiest way to start is by using the web interface to
>        configure your printer. Go to "http://localhost:631" and choose
>        the Administration tab at the top of the page.
> 
> Okay, but I want to access that (on enoch, the new 15 install box)
> from bogus, my current 14.2 main machine.  Try http://enoch:631.

  And can you ping enoch? You don't need a FQDN (enoch.private or
enoch.mynet or something like that)?

>    The connection was refused when attempting to contact enoch:631
> 
> I haven't started ip_tables yet so no firewall.
> 
> cupsd is running:
> 
>     enoch% pgrep cupsd
>     1055
> 
> I've tried changing /etc/cups/cupsd.conf and /etc/inetd.conf in
> various ways (and restarting inetd or cupsd after any change) with no
> improvements.
> 
> cupsd.conf:
> 
>    # Only listen for connections from the local machine.
>    Listen localhost:631
>    Listen /var/run/cups/cups.sock
> 
>    # mds -- Also listen for conns from bogus;
>      Listen 192.168.0.15:631

  The only Listen line my cupsd.conf has is the cups.sock one. It also
has a Port line:

Port 631

Does yours have that?

> Using any of ip address (above), hostname (bogus) or *  gives same
> non-result.  Moreover, the cupsd.conf directive to listen doesn't show
> up in lsof:
> 
> enoch-root$ lsof -i:631 -sTCP:LISTEN
> 
> COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
> cupsd   1055 root    5u  IPv6  32275      0t0  TCP localhost:ipp
> (LISTEN)
> cupsd   1055 root    6u  IPv4  32276      0t0  TCP localhost:ipp
> (LISTEN)
> 
> What about inetd?  Adding to /etc/inetd.conf a line like:
> 
>   ipp  stream  tcp  nowait  root   /usr/sbin/tcpd  /usr/sbin/cupsd

  I don't have any reference to cups or printing at all in my
inetd.conf.

> doesn't make any difference.
> 
> It seems I'm trying to do something that can't be done.  Or that needs
> a magic incantation I don't know about.  Can I access cupsd:631 on
> enoch from bogus over the LAN?  Or not?

  Sure you can. I find cups a bit persnickety, though, especially about
network hostnames. When I try to print using my server's hostname in
the client setup, it often doesn't work. But if I use the IP address,
it has a much higher chance of success.
  Yes, I know, you haven't even got to that stage yet. You're still
trying to configure the server itself. But anyhow...
  Still, just now, for a test, I tried accessing my cups server by
hostname with firefox, and it failed with "Bad request". So I tried
again using the IP address instead, and it worked perfectly.

> I have to go make ginger chicken.

  Who's this Ginger? If I see him/her running in terror, I'll know you
were successful.

-- 


----- Dig the NEW and IMPROVED news sig!! -----


-------------- Shaggy was here! ---------------
              Ain't I'm a dawg!!

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | alt.os.linux.slackware

csiph-web