From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CUPS server cannot be contacted
Date: Thu, 14 Sep 2006 18:02:40 -0700 [thread overview]
Message-ID: <5bdc1c8b0609141802o2cde3a15lf88553f26004cdc3@mail.gmail.com> (raw)
In-Reply-To: <200609141415.00108.bulliver@badcomputer.org>
On 9/14/06, darren kirby <bulliver@badcomputer.org> wrote:
> quoth the Mark Knecht:
> > and this
> >
> > #Port 631
> > Port localhost:631
> >
> > or this
> >
> > Port 631
> > #Port localhost:631
>
> Which of these do you have in your file? I found just yesterday that
>
> Port 631
>
Same as your working version:
lightning ~ # cat /etc/cups/cupsd.conf | grep 631
# default IPP port of 631. It changes users whenever an external
# Ports/addresses that we listen to. The default port 631 is reserved
# Port 631
# Listen hostname:631
# Listen 1.2.3.4:631
Port 631
#Port localhost:631
#BrowsePort 631
lightning ~ #
lightning ~ # lpq
lpq: Unable to contact server!
lightning ~ # /etc/init.d/cupsd start
* Starting cupsd ...
[ ok ]lightning ~ # lpq
lpq: Unable to contact server!
lightning ~ #
I've seen this before, actually, when the Mac was turned off.
Linux/Gnome would only see the local CUPS server after it had seen the
remote server on the Mac.
I'm thinking that the system (some part of it anyway) has cached
the fact that the Mac had a CUPS server somewhere. Now that the Mac is
gone it cannot move forward. I have no data to back up that idea
though and I have no idea how to prove it true or false...
- Mark
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-15 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 15:30 [gentoo-user] CUPS server cannot be contacted Mark Knecht
2006-09-14 21:14 ` darren kirby
2006-09-15 1:02 ` Mark Knecht [this message]
[not found] ` <200609141839.21894.bulliver@badcomputer.org>
2006-09-15 2:08 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bdc1c8b0609141802o2cde3a15lf88553f26004cdc3@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox