public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: CUPS not allowing configuration from browser
Date: Thu, 9 Feb 2006 17:41:36 -0800	[thread overview]
Message-ID: <5bdc1c8b0602091741t70d4e241m7a7ac69691b6798@mail.gmail.com> (raw)
In-Reply-To: <43EBEAC2.8060708@mclure.org>

On 2/9/06, Manuel McLure <manuel@mclure.org> wrote:
> Mark Knecht wrote:
> > Hi Brett,
> >    Yes, I zapped it and tried restarting it but I get complaints.
>
>
> Try
>
> pgrep cupsd
>
> and see if there's a PID listed. If so, do
>
> pkill cupsd
> /etc/init.d/cupsd zap
> /etc/init.d/cupsd start

Good so far:

mark@lightning ~ $ su -
Password:
lightning ~ # pgrep cupsd
8015
lightning ~ # pkill cupsd
lightning ~ # /etc/init.d/cupsd zap
lightning ~ # /etc/init.d/cupsd start
 * Starting cupsd ...                                                     [ ok ]
lightning ~ #

I then go to http://localhost:631 and choose Manage Printers. I see
both printers which are on the network. One is on my son's FC2
machine, and is currently default. I also see the printer on the Mac.
I clock on the Mac printer's 'Set as default' button. I'm taken to a
page that says:

Forbidden
You don't have permission to access the resource on this server.

This doesn't happen on the 'Print Test page' button. That one
correctly sends a test page to each printer. However all other buttons
result in the message above. The used to allow me to type in a
password and do what I needed.

I'm still quite concerned that the cupsd config files are hosed. As
I've said there is nothing in the printers.conf file except a couple
of header lines.

>
> What's probably happened is that etc-update updated the
> /etc/init.d/cupsd script so it changes the location where it stores the
> PID it has to kill when you do a "stop", therefore running
> /etc/init.d/cupsd fails to kill the actual cupsd process. Since a cupsd
> is already running (the old cupsd) you can't start a new one since
> they'd compete for ports.
>
> For this reason I usually do a "/etc/init.d/<service> stop" before
> allowing etc-update to update any file in /etc/init.d, and then start it
> again after the update.


Probably a good idea.

Thanks,
Mark

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-10  1:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-10  0:36 Re: [gentoo-user] Re: CUPS not allowing configuration from browser brettholcomb
2006-02-10  1:04 ` Mark Knecht
2006-02-10  1:22   ` Manuel McLure
2006-02-10  1:41     ` Mark Knecht [this message]
2006-02-10  1:57       ` Manuel A. McLure
2006-02-10  2:34         ` Mark Knecht
2006-02-10  2:40           ` Mark Knecht
2006-02-10  4:23             ` Manuel A. McLure
2006-02-10 19:06               ` Mark Knecht
2006-02-10 22:15                 ` Manuel McLure
  -- strict thread matches above, loose matches on Subject: below --
2006-02-09  3:37 [gentoo-user] " Mark Knecht
2006-02-09 11:38 ` [gentoo-user] " Harry Putnam
2006-02-09 13:02   ` Mark Knecht
2006-02-09 13:18     ` Jean Magnan de Bornier
2006-02-09 13:32     ` Sarpy Sam
2006-02-09 22:12     ` Nick Rout
2006-02-10  0:27       ` 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=5bdc1c8b0602091741t70d4e241m7a7ac69691b6798@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