Does your fix stop this from happening? I'm not entirly sure it's the same issue as I reported in that mail I linked to, but it certainly looks like a bug.
If you're fix works, I suggest creating a ticket with the patch. Good work :) On 29/01/2009, Greg <[email protected]> wrote: > > I've managed to reproduce the problem fairly consistently by running > several symfony batch scripts simultaneously after doing a clear- > cache, essentially simulating a busy web server. > > { ./symfony cc; php batch/generate_config_cache.php & php batch/ > generate_config_cache.php & php batch/generate_config_cache.php & php > batch/generate_config_cache.php & php batch/generate_config_cache.php > & php batch/generate_config_cache.php & } > > Where the batch/generate_config_cache.php file is: > -------------------------------------------------------------------------------- > <?php > > define('SF_ROOT_DIR', realpath(dirname(__FILE__).'/..')); > define('SF_APP', 'frontend'); > define('SF_ENVIRONMENT', 'dev'); > define('SF_DEBUG', false); > > require_once > (SF_ROOT_DIR.DIRECTORY_SEPARATOR.'apps'.DIRECTORY_SEPARATOR.SF_APP.DIRECTORY_SEPARATOR.'config'.DIRECTORY_SEPARATOR.'config.php'); > > echo "Configuration generated and cached for " . SF_APP . "\n"; > > exit(0); > --------------------------------------------------------------------------------------------------- > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
