Bug #16548 Updated: exec or system a daemon will catch the port for this session

From: Date: Wed, 24 Apr 2002 11:45:45 +0000
Subject: Bug #16548 Updated: exec or system a daemon will catch the port for this session
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-5808@lists.php.net to get a copy of this message
ID: 16548 Updated by: stefan.marquardt@hagebau.de Reported By: stefan.marquardt@hagebau.de -Status: Closed +Status: Open Bug Type: Session related Operating System: RED HAT Linux 7.2 PHP Version: 4.1.2 New Comment: Found new error in latest cvs: This line system("$SDHAG/ha-server $DB $CADB $CABI 1 $SDHAG 2>&1",$ret); has 0 100% as returncode i put an echo before exit 0! With older php there was now error. Previous Comments: ------------------------------------------------------------------------ [2002-04-23 19:55:08] sniper@php.net This should be fixed in CVS. Please try the latest cvs snapshot from http://snaps.php.net/ and make sure the Revision of ext/session/mod_files.c is 1.74 --Jani ------------------------------------------------------------------------ [2002-04-18 16:30:18] sniper@php.net reopened as possible session related bug. ------------------------------------------------------------------------ [2002-04-18 10:30:13] stefan.marquardt@hagebau.de Sorry ! PHP/4.2.0RC4 has the same problem with _mprshut and session.auto_start = 1. httpd and _mprshut acces /tmp/sess_* ------------------------------------------------------------------------ [2002-04-18 09:39:10] sniper@php.net Please try PHP 4.2.0RC4 from http://www.php.net/~derick/ ------------------------------------------------------------------------ [2002-04-17 10:01:27] stefan.marquardt@hagebau.de Now it's 100% true: Without session.auto_start = 0 it works also with apache with php compiled. So i can't use session variables. Has anybody interest to solve the problem ? I know not much from C. On which side is the error ? PHP or _mproshut (Progress) ? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/16548 -- Edit this bug report at http://bugs.php.net/?id=16548&edit=1

« previous php.bugs (#5808) next »