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

ID: 16548 Updated by: sniper@php.net Reported By: stefan.marquardt@hagebau.de -Status: Open +Status: Closed Bug Type: Session related Operating System: RED HAT Linux 7.2 PHP Version: 4.1.2 New Comment: 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 Previous Comments: ------------------------------------------------------------------------ [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) ? ------------------------------------------------------------------------ [2002-04-17 07:23:29] stefan.marquardt@hagebau.de Without session.auto_start = 0 it works without problem ! (it was 1 but i use it) [root@linux /tmp]# fuser sess* sess_e2b04b5ddbae91f2c52fd86e808565f5: 20658 20661 20664 20667 [root@linux /tmp]# ps -ef | grep 20658 root 20658 1 0 12:15 ? 00:00:00 /home/dlc83e/bin/_mprshut /home/ root 20672 12474 0 12:15 pts/1 00:00:00 grep 20658 _mprshut access the session file in /tmp ! How can this happen ? ------------------------------------------------------------------------ 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