installing php5-curl reloads apache *before* it's set up
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
php5 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
php5-curl tries to reload apache when it's installed. I assume the idea is to make the curl module available immediately. But the reload comes too early - before php5-curl is set up. So I had to reload apache manually in order to start using curl.
Maybe I'm wrong and there's some other reason for the reload :). It seems a pity to have to do the manual reload though, when we're already seeing one automatic reload happen.
To see whether curl was enabled, I used a simple test PHP file:
<?php phpinfo(); ?>
visited it in my web browser, and searched for "curl".
Here's the transcript. If you already have php5-curl installed, you'll need to *purge* it ("Remove completely"), before you can reproduce this.
$ sudo apt-get install php5-curl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
php5-curl
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/28.0 kB of archives.
After this operation, 118 kB of additional disk space will be used.
Selecting previously unselected package php5-curl.
(Reading database ... 213411 files and directories currently installed.)
Unpacking php5-curl (from .../php5-
Processing triggers for libapache2-mod-php5 ...
* Reloading web server config apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 10.184.27.62 for ServerName
Setting up php5-curl (5.3.10-1ubuntu3.2) ...
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: php5-curl 5.3.10-1ubuntu3.2
ProcVersionSign
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Mon Jul 16 16:35:42 2012
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: php5
UpgradeStatus: No upgrade log present (probably fresh install)
This sounds familiar - I think that on first install of a new module a 'restart' is required rather than 'reload'.
It can also be resolved by a second 'reload' from memory - I will check.