Your message dated Thu, 23 Aug 2012 09:25:33 +0200
with message-id
<caljhhg-4tcasqqkrhusb5guuyoyo+uzfaradc_znjiofi0-...@mail.gmail.com>
and subject line Re: [php-maint] Bug#621360: /etc/cron.d/php5 wreaks havoc on
session-based PHP apps
has caused the Debian Bug report #621360,
regarding /etc/cron.d/php5 wreaks havoc on session-based PHP apps
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
621360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621360
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php5
Version: 5.3.2-1ubuntu4.2
Severity: important
The cron job assumes that all PHP scripts use the global max lifetime value. I
have never, once, ever seen a PHP script that recommends using the default
settings as a good idea. For example, I am using SugarCRM. The cron job is
blindly vaporizing session data every 30 minutes despite the fact that SugarCRM
changes this value locally. The effect this has is devastating to the
operation of SugarCRM. Ajax calls into the application often get redirected to
a login dialog due the the session disappearing at inappropriate times. When
this occurs it causes data loss in the application.
Also, it seems inappropriate to me to change the global php.ini setting at all
for any reason. Those are very reasonable defaults. However, within Apache
you may want to locally modify the max lifetime for a particular vhost to a
value which is unreasonable to other vhosts. Such as SugarCRM where we want
sessions to last an entire 8 hour shift.
I question whether this cron job serves any purpose at this point. It seems to
be working around a bug in the Debian PHP 4.0 package from2004. I have been
testing today and PHP 5.3 appears to be garbage collecting sessions
appropriately. The permissions seem to suggest there should be no problems, as
well.
The original Debian Bugs which prompted the addition of the cron job and move
of session data to /var/lib/php[4|5] are #256831 and #257111
Sorry, the system info is probably a bit ugly as this is an Ubuntu system but
the problem originates from Debian so I chose to submit to debian bts.
-- System Information:
Debian Release: squeeze/sid
APT prefers lucid-updates
APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-21-server (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages php5 depends on:
ii libapache2-mod-php5 5.3.2-1ubuntu4.2 server-side, HTML-embedded scripti
ii php5-common 5.3.2-1ubuntu4.2 Common files for packages built fr
php5 recommends no packages.
php5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> I see that bug #590485 fixes the cron job so I can use conf.d to override.
> So I could just override the global defaults by having my sugarcrm package
> install a config file fragment.
--
Ondřej Surý <[email protected]>
--- End Message ---
