From: "Mark Haney" <mhaney@ercbroadband.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] Re: Re: cupsd wont start on boot.
Date: Mon, 07 Aug 2006 08:20:45 -0400 [thread overview]
Message-ID: <44D7301D.1080404@ercbroadband.org> (raw)
In-Reply-To: <eb5tfe$kkp$1@sea.gmane.org>
Duncan wrote:
> "Mark Haney" <mhaney@ercbroadband.org> posted
> 44D66CC4.6060307@ercbroadband.org, excerpted below, on Sun, 06 Aug 2006
> 18:27:16 -0400:
>
>>> what happens if you invoke the init script directly, ie not running the
>>> commands contained within the script...
>>>
>>> /etc/init.d/cupsd start
>>>
>> \
>> This is what I get:
>>
>> * Caching service dependencies ...
>> [ ok ]
>> * WARNING: "cupsd" has already been started.
>>
>> But it's not started.
>>
>
> Ahhh!
>
> Try /etc/init.d/cupsd zap
>
> /then/
>
> /etc/init.d/cupsd start
>
>
> The "zap" thing is there to zap stale tracking files left behind in a
> crash or something. If it says it's started when it's not, that's
> always the first thing to try.
>
Well I'll be. That worked. Except it still gives me the 'Child Exited'
error on a reboot. It's like cupsd isn't /stopping/ correctly (or at
all) on a shutdown.
--
Me transmitte sursum, caledoni!
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-07 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 14:00 [gentoo-amd64] cupsd wont start on boot Mark Haney
2006-08-05 5:50 ` [gentoo-amd64] " Duncan
2006-08-06 15:46 ` Paul de Vrieze
2006-08-06 22:15 ` Neil Stone
2006-08-06 22:23 ` Mark Haney
2006-08-06 22:27 ` Mark Haney
2006-08-06 23:20 ` [gentoo-amd64] " Duncan
2006-08-07 12:20 ` Mark Haney [this message]
2006-08-07 16:19 ` [gentoo-amd64] " Duncan
2006-08-06 23:24 ` [gentoo-amd64] " Bob Slawson
2006-08-07 0:31 ` Ferris McCormick
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=44D7301D.1080404@ercbroadband.org \
--to=mhaney@ercbroadband.org \
--cc=gentoo-amd64@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