#22526 [Com]: session_start/popen hang

2003-07-21 Thread spoon at nexdot dot net
 ID:   22526
 Comment by:   spoon at nexdot dot net
 Reported By:  iberry at raxnet dot net
 Status:   No Feedback
 Bug Type: Session related
 Operating System: Windows 2000
 PHP Version:  4.3.2
 New Comment:

I am a user of the program iberry has developed and I can confirm that
the negative result is still occuring in updated versions of php (i use
a nightly updated php5.0.0 (it is currently post beta1).

CMD.EXE and Apache.EXE hang and if you end the session with the site,
and come back, it will work (in a new child process, leaving the now
hanging ones stay there as ghosts. If you stop apache service and
restart it, its fine untill you attempt the session and popen
combinations).


Previous Comments:


[2003-07-20 10:36:01] [EMAIL PROTECTED]

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to Open. Thank you.





[2003-07-12 23:42:45] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5-win32-latest.zip

And update the version if this still happens.




[2003-06-24 03:33:56] marcus at quintic dot co dot uk

I have exactly the same problem with fopen+fpassthru instead of popen
(just filed a bug that got closed as a duplicate #24295) on Windows XP.
It makes session-based authentication next to useless for an app we are
developing. CGI does not cure it, neither does disabling the trans_sid.
The bug is apparent in 4.2.x and upwards in our case (on Apache 1.3.27)



[2003-06-06 11:03:10] mobrien at milleker dot org

Same problem observed in 4.3.2 on Win2K with Apache 1.3.1

Benny - Read the section in the install.txt about running in CGI mode
(if you have not already): this is a completely unacceptable situation
for production environments, IMO.



[2003-06-02 06:21:56] bbubble622 at yahoo dot com

Finally I was able to switch to CGI based PHP.
Although it is (very) slow, it gives the right results !

-benny



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/22526

-- 
Edit this bug report at http://bugs.php.net/?id=22526edit=1



#22662 [Com]: shell_exec not working on windows XP

2003-06-04 Thread spoon at nexdot dot net
 ID:   22662
 Comment by:   spoon at nexdot dot net
 Reported By:  pjaleysen at hotmail dot com
 Status:   Open
 Bug Type: Program Execution
 Operating System: Windows XP
 PHP Version:  4.3.2-RC
 New Comment:

This seems very close to what im experiencing.

I am using php 5.0.0-dev (updated about 2 weeks ago), but the problem
has occured for me on 4.x.x versions. I use Windows XP Pro/Windows 2000
Server with my 5.0.0-dev. Apache 2 24

When i use ANY of the MANY methods for passing a system call

System
Shell_exec
Exec
``  (backtick)
Passthru

they all act the same (in this case, as a passthru), UNLESS with a
native dos command (which i tried after reading this bug post).

The functions such as the 2 exec ones and the backticks should not
output anything. I do this:

$string=exec/shell_exec/``;

when calling something such as ping/dir/echo, or any normal dos
command, they work as expected... nothing is output to the browser (or
above the php header have you) unless i do an

echo $string;

When i try to call a program such as gzip, $string has a length of 0
(or null) and the the output from the command appears in my browser (or
above PHP headers if run from command line) without echo'ing. Other
special parts of each system call functions also do not work, such as
exec's array output, which is null unless a native dos command.


Previous Comments:


[2003-03-15 03:42:47] pjaleysen at hotmail dot com

Executing Windows-based applications work alright, but not the ones
running in DOS. e.g. I am using winzip now instead of pkzip.exe for
dos. 

Because I have to use windows application, it will mke the php code
less portable, since I have to use installed software



[2003-03-13 06:33:40] pjaleysen at hotmail dot com

Nope, paths, all of that excluded.I tried to put some details below,
comming from http://forums.devshed.com/t55038/s.html (which also deals
with the various path issues. Many others also had a look at it).

At the very end of the forum there is an assumption that it is a WinXP
problem, since win2000 works fine.



[2003-03-13 06:25:57] [EMAIL PROTECTED]

%PATH% issue? (blind guess)



[2003-03-13 03:01:51] pjaleysen at hotmail dot com

HI, I tried it out with PHP Version 4.3.2-RC but the problem remains;
native MS-DOS commands work fine, other DOS-applications do not
respond.

kind regards
Patrick



[2003-03-12 17:05:51] [EMAIL PROTECTED]

Yes, but the snapshot is 4.3.2-dev so try it out.
We're about to release 4.3.2 soon.





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/22662

-- 
Edit this bug report at http://bugs.php.net/?id=22662edit=1



#22794 [Bgs]: Apache fails to start, and produces no error

2003-03-20 Thread spoon at nexdot dot net
 ID:   22794
 User updated by:  spoon at nexdot dot net
 Reported By:  spoon at nexdot dot net
 Status:   Bogus
 Bug Type: Apache2 related
 Operating System: windows 2000 server
 PHP Version:  4CVS-2003-03-19 (stable)
 New Comment:

My 'dev' is pre rc1.


Previous Comments:


[2003-03-19 21:38:45] [EMAIL PROTECTED]

hi.
I'm a bit confused
the 'dev' version you are working with is the most current snapshot? or
a older one (when from)
you wouldn't have the window debugger available would you?



[2003-03-19 20:30:46] spoon at nexdot dot net

I have php4apache2.dll as the module that is being loaded on both
machines...

(if that is what you mean otherwise, there is no apache2handler.dll
if _that_ is what you mean)



[2003-03-19 18:04:22] [EMAIL PROTECTED]

It's now by default using the sapi/apache2handler.
Make sure your httpd.conf is configured properly.




[2003-03-19 17:59:58] spoon at nexdot dot net

This has happened with a few of the cvs versions (i try a few times a
week with latest stable snapshots) ever since RC1 was released
(4.3.2).

After appropriatley installing php (like usual) apache will fail to
start, and will produce no error on stdout, nor will it log anything
(unusual) in the apache error log besides its normal child process info
when it kills itself.

When i put back the php i had before it (4.3.2-dev according to php
-v), it works fine. I enabled error logging in RC1-cvs and no log was
produced during the failed apache starts.

I can reproduce this on 2 different server, one running Windows 2000
Server (the case im reporting), and on my home server running Windows
XP RC1. Both work on 4.3.2-dev, and fail on 4.3.2-RC1.




-- 
Edit this bug report at http://bugs.php.net/?id=22794edit=1



#22794 [NEW]: Apache fails to start, and produces no error

2003-03-19 Thread spoon at nexdot dot net
From: spoon at nexdot dot net
Operating system: windows 2000 server
PHP version:  4CVS-2003-03-19 (stable)
PHP Bug Type: Apache2 related
Bug description:  Apache fails to start, and produces no error

This has happened with a few of the cvs versions (i try a few times a week
with latest stable snapshots) ever since RC1 was released (4.3.2).

After appropriatley installing php (like usual) apache will fail to start,
and will produce no error on stdout, nor will it log anything (unusual) in
the apache error log besides its normal child process info when it kills
itself.

When i put back the php i had before it (4.3.2-dev according to php -v),
it works fine. I enabled error logging in RC1-cvs and no log was produced
during the failed apache starts.

I can reproduce this on 2 different server, one running Windows 2000
Server (the case im reporting), and on my home server running Windows XP
RC1. Both work on 4.3.2-dev, and fail on 4.3.2-RC1.
-- 
Edit bug report at http://bugs.php.net/?id=22794edit=1
-- 
Try a CVS snapshot: http://bugs.php.net/fix.php?id=22794r=trysnapshot
Fixed in CVS:   http://bugs.php.net/fix.php?id=22794r=fixedcvs
Fixed in release:   http://bugs.php.net/fix.php?id=22794r=alreadyfixed
Need backtrace: http://bugs.php.net/fix.php?id=22794r=needtrace
Try newer version:  http://bugs.php.net/fix.php?id=22794r=oldversion
Not developer issue:http://bugs.php.net/fix.php?id=22794r=support
Expected behavior:  http://bugs.php.net/fix.php?id=22794r=notwrong
Not enough info:http://bugs.php.net/fix.php?id=22794r=notenoughinfo
Submitted twice:http://bugs.php.net/fix.php?id=22794r=submittedtwice
register_globals:   http://bugs.php.net/fix.php?id=22794r=globals
PHP 3 support discontinued: http://bugs.php.net/fix.php?id=22794r=php3
Daylight Savings:   http://bugs.php.net/fix.php?id=22794r=dst
IIS Stability:  http://bugs.php.net/fix.php?id=22794r=isapi
Install GNU Sed:http://bugs.php.net/fix.php?id=22794r=gnused



#22794 [Bgs]: Apache fails to start, and produces no error

2003-03-19 Thread spoon at nexdot dot net
 ID:   22794
 User updated by:  spoon at nexdot dot net
 Reported By:  spoon at nexdot dot net
 Status:   Bogus
 Bug Type: Apache2 related
 Operating System: windows 2000 server
 PHP Version:  4CVS-2003-03-19 (stable)
 New Comment:

I have php4apache2.dll as the module that is being loaded on both
machines...

(if that is what you mean otherwise, there is no apache2handler.dll
if _that_ is what you mean)


Previous Comments:


[2003-03-19 18:04:22] [EMAIL PROTECTED]

It's now by default using the sapi/apache2handler.
Make sure your httpd.conf is configured properly.




[2003-03-19 17:59:58] spoon at nexdot dot net

This has happened with a few of the cvs versions (i try a few times a
week with latest stable snapshots) ever since RC1 was released
(4.3.2).

After appropriatley installing php (like usual) apache will fail to
start, and will produce no error on stdout, nor will it log anything
(unusual) in the apache error log besides its normal child process info
when it kills itself.

When i put back the php i had before it (4.3.2-dev according to php
-v), it works fine. I enabled error logging in RC1-cvs and no log was
produced during the failed apache starts.

I can reproduce this on 2 different server, one running Windows 2000
Server (the case im reporting), and on my home server running Windows
XP RC1. Both work on 4.3.2-dev, and fail on 4.3.2-RC1.




-- 
Edit this bug report at http://bugs.php.net/?id=22794edit=1