h3x.no

1:  post_max_size >= 2GB makes PHP overflow, resulting in a negative post_max_size:
“POST Content-Length of 0 bytes exceeds the limit of -2147483648 bytes”

2: defining post_max_size (etc) with MB instead of M causes PHP to only read the last character, in other words 10MB becomes 10 bytes . How hard can it be to either use the first character or even better, both?

(note 1: this can be avoided by actually reading the manual, but this should have been handled better from PHP`s side IMO)

(Note 2: This experience come from the latest stable PHP version in SLES 10SP2, hopefully this has been fixed in later releases.)

Here is a simple code PHP snippet to display the clock each 10 minutes x times in the format of:

php5 test.php
20:40
20:50
21:00
21:10
21:20
21:30
21:40

Etc.

<?php

$j = 0;
for($i=0;$i<10;$i+=1) {
        $j += (10*60);
        $hour = date("H", (time()+$j));
        $min  = ceil((date("i", (time()+$j))/10))*10;
        if($min > 50) {
                $min = "00";
                $hour++;
        }
        echo $hour.":".$min."\n";
}

?>