Issues with session files and fork/exec/popen (Fw: Bug #16548)

From: Date: Wed, 17 Apr 2002 19:51:13 +0000
Subject: Issues with session files and fork/exec/popen (Fw: Bug #16548)
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-82925@lists.php.net to get a copy of this message
Hey, does anyone out there know what could be causing this problem? It looks like the fd for the session file is kept open when the process is forked/exec'ed, and that in turn (somehow?) keeps the apache socket for port 80 open, preventing further http requests from being processed. Could this be solved by setting the close-on-exec flag of the session file descriptor? It a really strange problem, I just wondered if anyone had heard of this before, or has a solution! --Wez. > ID: 16548 > Bug Type: Apache related > Operating System: RED HAT Linux 7.2 > PHP Version: 4.1.2 > New Comment: > > 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) ? > [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

« previous php.dev (#82925) next »