From: "Kevin O'Gorman" <kogorman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Oddities in apache2 update, other init bizarrity.
Date: Tue, 4 Sep 2007 19:55:44 -0700 [thread overview]
Message-ID: <9acccfe50709041955ke87aa8yc40f432102b4bd9@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
Stable x86 just got a new apache server, and it's puzzling me.
For one thing, /etc/conf.d/apache2 now ends with this
# Environment variables to keep
# All environment variables are cleared from apache
# Use this to preserve some of them
# NOTE!!! It's very important that this contains PATH
# TODO: Phase this out in favor of /etc/conf.d/env_whitelist
#KEEPENV="PATH"
It has said all along that it's important to have PATH, but now it's
commented out without any replacement in env_whitelist.
Moreover, there's no example in env_whitelist to show the syntax. I just
put PATH in there on a line of its own, and hoped for the best.
The bigger puzzle is this one: I can't stop apache because it can't be
found, but I also can't start it because it's already running. It is in
fact running and serving web pages. But I'd like the init stuff to be a lot
more consistent.
The confusion about cupsd and vmware is a separate issue I've been meaning
to ask about for months; I don't think it has anything to do with apache2.
treat ~ # cd /etc/init.d
treat init.d # ./apache2 stop
* Stopping apache2 ...
No /usr/sbin/apache2 found running; none
killed.
[ !! ]
treat init.d # ./apache2 start
* WARNING: apache2 has already been started.
treat init.d # ./apache2 status
* Caching service dependencies ...
* Service 'cupsd' should be AFTER service 'vmware', but one of
* the services 'vmware' depends on, depends on
'cupsd'!
[ ok ]
* status: started
treat init.d #
--
Kevin O'Gorman, PhD
[-- Attachment #2: Type: text/html, Size: 3133 bytes --]
next reply other threads:[~2007-09-05 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 2:55 Kevin O'Gorman [this message]
2007-09-05 15:21 ` [gentoo-user] Oddities in apache2 update, other init bizarrity Dan Farrell
2007-09-05 16:27 ` Grant
2007-09-05 17:19 ` Dan Farrell
2007-09-05 17:20 ` Dan Farrell
[not found] ` <32F9A50E9B2B5A4AA062A602121DD4F00629C567@USEA-EXCH3.na.uis.unisys.com>
2007-09-05 18:12 ` [gentoo-user] Apache2 2.0 -> 2.2 upgrade Dan Farrell
2007-09-05 18:39 ` Dan Farrell
2007-09-05 18:57 ` Christian Heim
2007-09-05 20:11 ` Dan Farrell
2007-09-05 18:42 ` Christian Heim
2007-09-05 19:06 ` Dan Farrell
2007-09-05 19:26 ` [gentoo-user] Apache2 2.0 -> 2.2 upgrade [solved] Dan Farrell
[not found] ` <20070905124003.14f99ca1@pascal.spore.ath.cx>
2007-09-05 20:23 ` [gentoo-user] Oddities in apache2 update, other init bizarrity Grant
2007-09-05 22:16 ` Dan Farrell
2007-09-05 22:34 ` kashani
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=9acccfe50709041955ke87aa8yc40f432102b4bd9@mail.gmail.com \
--to=kogorman@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