From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] [#14254] FAILED (try 7) apache.git=1.3.41rusPL30.23-alt8 mod_ssl.git=2.8.31-alt2.1
Date: Thu, 15 Oct 2009 00:27:15 +0400
Message-ID: <20091014202715.GE29915@wo.int.altlinux.org> (raw)
In-Reply-To: <20091014144034.GA31343@mw.office.seiros.ru>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Wed, Oct 14, 2009 at 06:40:34PM +0400, Денис Смирнов wrote:
[...]
> Если установлен mod_ssl, то он меняет конфиг апача.
> Если после этого сертификатов нет -- апач склеивает ласты, т.е. не
> проходит даже проверку конфигов.
>
> По крайней мере mod_php5, как оказалось, при установке выполняет нечто,
> что просит апача проверить конфиги.
>
> Результат: apt-get install mod_ssl mod_php5 обламывается.
>
> Варианта есть два:
> - найти везде где проверяется конфиг апача до собственно запуска апача, и
> оторвать это нафиг;
> - таки создавать эти ключики и в %post тоже, но в профилях mkve с помощью
> hook'а их удалять;
To ensure that necessary certificates are created before these config
checks, I'd suggest to extend the code that checks apache configs.
For example, just call an external program that generates certificates.
BTW, your change to httpd.init.2_3 does exactly that: you added
appropriate calls to conftest() and start(). But you said that
mod_php5 still does not work. Why does it happen? Looks like
mod_php5 uses own method to check apache configuration and
bypasses the code you added.
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-14 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 12:02 ` Denis Smirnov
2009-10-14 12:45 ` Dmitry V. Levin
2009-10-14 14:40 ` Денис Смирнов
2009-10-14 19:40 ` Michael Shigorin
2009-10-15 12:00 ` Денис Смирнов
2009-10-14 20:27 ` Dmitry V. Levin [this message]
2009-10-15 12:02 ` Денис Смирнов
2009-10-14 14:02 ` Alexey I. Froloff
2009-10-14 14:42 ` Денис Смирнов
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=20091014202715.GE29915@wo.int.altlinux.org \
--to=ldv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git