[PHP-DEV] Bug #11592: need for an a SIGALRM based timeout mecanism

2001-06-20 Thread thomas . morin
From: [EMAIL PROTECTED] Operating system: irrelevant PHP version: 4.0.5 PHP Bug Type: Feature/Change Request Bug description: need for an a SIGALRM based timeout mecanism As mentionned in #9676, in #8595 and in comments in the set_time_limit function online manual page,

[PHP-DEV] Bug #12266: max execution time reached during session_start with mm session handler

2001-07-19 Thread thomas . morin
From: [EMAIL PROTECTED] Operating system: Linux PHP version: 4.0.6 PHP Bug Type: Session related Bug description: max execution time reached during session_start with mm session handler In have a bunch of those errors in my logs : PHP Fatal error: Maximum execution

[PHP-DEV] Bug #12267: Session (concurrency ?) problem

2001-07-19 Thread thomas . morin
From: [EMAIL PROTECTED] Operating system: Linux PHP version: 4.0.6 PHP Bug Type: Unknown/Other Function Bug description: Session (concurrency ?) problem While testing a php apllication, I found that I had some trouble with session variables (php4 native sessions, not

[PHP-DEV] Bug #12267 Updated: Session (concurrency ?) problem

2001-07-19 Thread thomas . morin
ID: 12267 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Old Bug Type: Unknown/Other Function Bug Type: Session related Operating System: Linux PHP Version: 4.0.6 New Comment: Sorry for the layout, my 2 columns are broken. I also changed the 'Type' of the bug to

[PHP-DEV] Bug #12267 Updated: Session (concurrency ?) problem

2001-07-19 Thread thomas . morin
ID: 12267 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Session related Operating System: Linux PHP Version: 4.0.6 New Comment: The fact is a similar problem is happening with the mm module, but here I can't insert error_log to be sure... is this

[PHP-DEV] Bug #12267 Updated: Session (concurrency ?) problem

2001-07-20 Thread thomas . morin
ID: 12267 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Session related Operating System: Linux PHP Version: 4.0.6 New Comment: I would tend to think that : - make the file session handler race safe- make the mm session handler race safe - make the a

Re: [PHP-DEV] Bug #12267 Updated: Session (concurrency ?) problem

2001-07-20 Thread Thomas Morin
Hi Sascha, Thanks for your answer, I now understand better why locking is not made at a lower level. And you are right, I don't have a proposal for general locking, I don't know php nor C nor Apache enough. However, I really think it would be better to document this somewhere. If it is a

Re: [PHP-DEV] Bug #12267 Updated: Session (concurrency ?) problem

2001-07-24 Thread Thomas Morin
Hello Sascha, Well... In the current case, even if it is not the cleanest solution, calling session_end before making the redirection would solve my problem in a acceptable manner. The model described in this function documentation is nice, and the existence of session_end and

[PHP-DEV] Re: session_end/session_readonly

2001-07-31 Thread Thomas Morin
Hi, Daniel Gustafsson wrote: Maybe this have been discussed but I can't seem to find anything inthe archives or on the net. Related : - Post to -dev titled Re: session_readonly() documented but not implemented?! (22/07/2001) - Bug #12267 (and followups in -dev) According to the CVS logs,