It's the standard session handler with a custom session_save_path being set.

Oddly, the problems go away if I use the standard save path. However this isn't a practical option for this app as the developers hard-coded the save path into pretty much every file in the (rather large) application rather than, I dunno, using an include or something logical. I considered grepping this out, but I can see this ending in tears as the app is large, old and complex. I'd rather restrict my changes to the section in question rather than making wholesale changes to the app and then being responsible for whatever goes wrong.

I checked out those PHP bugs you mentioned earlier - hard to say if these are what is causing the problem or not. I also read some posts saying that flock doesn't work on some NFS filesystems. I have no idea if this server is running NFS or not (assuming I need shell access to be able to find out), but it would make sense if this previously-reliable script suddenly broke when the host upgraded their storage systems.

So for now the best I have been able to come up with is this...

<iframe src="file1.php?delay=500" ></iframe>
<iframe src="file2.php?delay=1500" ></iframe>
<iframe src="file3.php?delay=2500" ></iframe>

The delay variable is used to have a little sleep just before calling session_start() - basically forcing the iframes to load in series (which in my case, they aren't doing naturally). This isn't a fantastic solution in a number of senses, but it's also the best I have after 8+ hours and there comes a point when one must admit defeat and accept the dirty-hack solution as preferable to working for McWages and upsetting every other client by delaying their work. I just reached that point.

Thanks for your help on this Tim + others, your wisdom made it a lot easier to understand what was happening here.

Harvey.

On 6/04/2011 10:39 p.m., Tim Oliver wrote:
On Wed, Apr 6, 2011 at 6:58 PM, Harvey Kane<[email protected]>  wrote:

Are you using the default files session handler, or is there a custom
one auto_prepended or otherwise installed? Maybe it's not implementing
destroy properly.

http://bugs.php.net/bug.php?id=47640 might be interesting too.

Also, check out http://bugs.php.net/bug.php?id=47640



--
Harvey Kane

Phone:
- Auckland: +64 9 950 4133
- Wanaka: +64 3 746 8133
- Mobile: +64 21 811 951

Email: [email protected]
 If you need to contact me urgently, please read my email policy 
www.ragepank.com/email/

--
NZ PHP Users Group: http://groups.google.com/group/nzphpug
To post, send email to [email protected]
To unsubscribe, send email to
[email protected]

Reply via email to