Last modified: 2010-05-15 16:03:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19222, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17222 - eAccelerator determines not properly
eAccelerator determines not properly
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.13.x
All All
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://adminuser.wordpress.com/2008/0...
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-29 07:57 UTC by wikigeek
Modified: 2010-05-15 16:03 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description wikigeek 2009-01-29 07:57:37 UTC
/config/index.php :

$conf->eaccel = function_exists( 'eaccelerator_get' );
if ( $conf->eaccel ) {
	$conf->turck = 'eaccelerator';
	print "<li><a href=\"http://eaccelerator.sourceforge.net/\">eAccelerator</a> installed</li>\n";
}

it's wrong, because function 'eaccelerator_get' disabled.

For more information see http://adminuser.wordpress.com/2008/01/15/fatal-error-unknown-function-eaccelerator_get-in-somefile/
Comment 1 Chad H. 2009-01-29 21:35:07 UTC
Seeing as the MW wrapper for eAccelerator (eAccelBagOStuff, defined in BagOStuff.php) uses eaccelerator_get(), I think this is a good choice. We don't want to configure that it's ok, only to later find out we can't use it (although the cache setup handles it too :)

Is there a function we should be using instead of eaccelerator_get(), since it does in fact seem to be disabled by default?
Comment 2 Tim Starling 2009-01-30 07:57:58 UTC
Our code is correct, if the object cache is disabled then we can't use it. And note that it was disabled for good reason, if MediaWiki was configured to use eaccelerator as an object cache, it could trigger the DoS referred to in http://eaccelerator.net/ticket/37

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links