Bug#504053: also fails to pick up values in /etc/php5/conf.d

[Chris Butler]

The cron job also fails to read files in /etc/php5/conf.d, so if the local
admin has overridden the default value using a file in conf.d then it won't
be picked up.

--
Chris Butler <chr...@debian.org>
GnuPG Key ID: 1024D/D097A261

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Raphael Geissert]

On Monday 27 April 2009 05:19:35 Chris Butler wrote:
> The cron job also fails to read files in /etc/php5/conf.d, so if the local
> admin has overridden the default value using a file in conf.d then it won't
> be picked up.

Please refer to #452347

Cheers,
--
Raphael Geissert - Debian Maintainer
www.debian.org - get.debian.net

[sean finney]

On Mon, Apr 27, 2009 at 02:08:28PM -0500, Raphael Geissert wrote:
> On Monday 27 April 2009 05:19:35 Chris Butler wrote:
> > The cron job also fails to read files in /etc/php5/conf.d, so if the local
> > admin has overridden the default value using a file in conf.d then it won't
> > be picked up.
>
> Please refer to #452347

fwiw, i don't really have a problem with expanding the glob to include
these files, but at the same time it's not too hard to invoke $EDITOR
on the cronjob, and even adding this feature won't solve all the
maxlifetime-related problems (even doing any kind of gc is problematic
with some apps who want to handle it themselves).

also, i'm not sure how this would complicate things with the upcoming
change in extension file layout stuff, so it's probably worth keeping it
tabled at least until then.

i guess in an ideal world there would be a way to invoke a php cmdline call
for eache sapi config and just have it run <?php echo ini_get(foo); ?>, but
unfortunately i think that the ini/conf.d is hardcoded at compile time for
each sapi.

sean

[Chris Butler]

First off, sorry for missing the other bug report about conf.d, I found the
first bug that looked appropriate and neglected to look further down!

On Mon, Apr 27, 2009 at 09:34:50PM +0200, sean finney wrote:
> i guess in an ideal world there would be a way to invoke a php cmdline call
> for eache sapi config and just have it run <?php echo ini_get(foo); ?>, but
> unfortunately i think that the ini/conf.d is hardcoded at compile time for
> each sapi.

I had a similar thought when I came across this problem. It turns out that
you can use the '-c' option to override the default config file location:

chrisb@cob:~$ php -c /etc/php5/apache2/php.ini -r 'print ini_get("session.gc_maxlifetime")."\n";'
1440
chrisb@cob:~$ php -c /etc/php5/cli/php.ini -r 'print ini_get("session.gc_maxlifetime")."\n";'
60

(values set differently for each SAPI for testing purposes)

The downside of this would be that you end up with a dependency on
php5-cli[1], although it would be easy enough to fall back on the current
method if the cli isn't installed.

[1] popcon suggests about 50% of php5 installations currently have php5-cli
installed

--
Chris Butler <chr...@debian.org>
GnuPG Key ID: 1024D/D097A261

--