Volker>> on Alpha, if you reach the 'memory limit' as imposed by the PHP.INI file, you get a nice error message.
That's my point.
>> If you specify an 'unreasonable' memory limit and actually try to reach that limit (by increasing the max. index value), the program 'silently' dies WITHOUT an error message
Well, I imagine where are flavors of mallocs going on. When simply allocating user data it may react different to failure then when allocating for some internal data structure.
Volker>> Although you would need to be using a real small PGFLQUOTA to hit that limit with index = 160000.
Yeah, for a simple fortran like array @ 4 bytes/integer with would be nothing. But this is probably implemented very dynamic/flexible with possibly a re-allocated element array and a malloc per element. So give is 32 bytes/object and it is still not much in total.
>> Capturing quota info is a little difficult as the PHP script fails almost immediately.
That's why you should focus on the SUCCESS cases, not the failures.
Of 20,000 is already too much, then try 8,000 and 16,000.
If 80K is too much then try 20k, 30K, 40K.
Rob>> For reference, here's the UAF quotas :-
Those looks like monkeys having thrown darts.
And they are likely to be overruled with SYSGEN PQL_M values.
FILLM is relatively low/scary.
TQ, WS settings low,
ASTLM/DIOLM high,
PGLFIL silly high.
Rob>> I guess I was looking for one of the quick wins that we sometimes get from the forums, and that one of you had come across this already.
Certainly. And Volker may have come through checking an other version.
Volker>> I've now installed CSWS_PHP V2.1 on OpenVMS I64 V8.2 and I cannot reproduce this problem.
Case closed! :-)
Volker>> Your PGFLQUOTA looks a little bit ridiculous (2.56 GB).
Ayup. Either clueless, or very smart (P2).
Grins,
Hein
