From: Christopher Slater <olyar@yahoo.com>
To: david.jay.jackson@wcox.com, linux-admin@vger.kernel.org
Subject: Re: Apache-2.0.35 Startup Errors
Date: Mon, 6 May 2002 08:27:15 -0700 (PDT) [thread overview]
Message-ID: <20020506152715.2500.qmail@web12808.mail.yahoo.com> (raw)
In-Reply-To: <200205011121.AA5046554@wcox.com>
I'm guessing here, but that sounds like Apache is set to use a lock
file in a directory that doesn't exist...
What do you get from a ls -l of /usr/local/http/logs/httpd.pid.
What about ls -ld /usr/local/http/logs
If the directory doesn't exist then try making it and see if it will
run then... Or get into your conf file and specify a different lock
file...
HTH,
Chris
--- David Jackson <david.jay.jackson@wcox.com> wrote:
> I compiled apache-2.0.35 without errors on Slackare-8.8, but when
> running
> apachectl start it fails with the followning erors:
>
>
> [Wed May 01 06:11:04 2002] [emerg] (22)Invalid argument: Couldn't set
> permission s on cross-process lock
> [Wed May 01 07:16:25 2002] [warn] pid file
> /usr/local/http/logs/httpd.pid overwr itten -- Unclean
> shutdown of previous Apache run?
> [Wed May 01 07:16:25 2002] [emerg] (22)Invalid argument: Couldn't set
> permission s on cross-process lock
>
>
> TIA,
> David
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
next prev parent reply other threads:[~2002-05-06 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 17:21 Apache-2.0.35 Startup Errors David Jackson
2002-05-06 15:27 ` Christopher Slater [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-06 16:53 David Jackson
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=20020506152715.2500.qmail@web12808.mail.yahoo.com \
--to=olyar@yahoo.com \
--cc=david.jay.jackson@wcox.com \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).