Re: PHP 4.0 Bug #10675 Updated: Executing background job from PHP causes session lock-up

This sounds as if it may be a disk caching issue. Is your session data stored in files (the default)? flush() dumps io to the web browser, is there a file_flush()? <millz@incogen.com> wrote in message news:20010504195453.8565.qmail@php2.chek.com... > ID: 10675 > User Update by: millz@incogen.com > Status: Open > Bug Type: *Session related > Description: Executing background job from PHP causes session lock-up > > Executed a perl script in the background like this: > perl scriptname.pl $otherParams 2> /dev/null 1> /dev/null > > Perl script forks and parent dies, so PHP "should" see the script as finished > immediately, perl child does work in background (takes a few minutes to run). > > PHP script that spawned perl script completes OK, browser stops waiting for more data from > php script as it should. > > However, when using the same browser window (or one from browser's file->new window) no > other pages that referrence the session will load in the browser. If we force the session > to destroy just after the system() call, other scripts load just fine. Also, other > scripts work just fine if we start a new browser from scratch (creates new session). > > So it appears that the PHP session is getting messed up somehow b/c of the background > system/exec/`` call. This seems to prevent the following pages from loading the session > properly and therefore they will not run. > > > One other thing, once the child perl script is finally complete everything starts working again, i.e.-the session is OK again. > > Previous Comments: > -------------------------------------------------------------------------- - > > [2001-05-04 15:22:47] millz@incogen.com > Executed a perl script in the background like this: > perl scriptname.pl $otherParams 2> /dev/null 1> /dev/null > > Perl script forks and parent dies, so PHP "should" see the script as finished immediately, perl child does work in background (takes a few minutes to run). > > PHP script that spawned perl script completes OK, browser stops waiting for more data from php script as it should. > > However, when using the same browser window (or one from browser's file->new window) no other pages that referrence the session will load in the browser. If we force the session to destroy just after the system() call, other scripts load just fine. Also, other scripts work just fine if we start a new browser from scratch (creates new session). > > So it appears that the PHP session is getting messed up somehow b/c of the background system/exec/`` call. This seems to prevent the following pages from loading the session properly and therefore they will not run. > > -------------------------------------------------------------------------- - > > > Full Bug description available at: > http://bugs.php.net/?id=10675 > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >