August 11th, 2010

„Every time you make a singleton, God kills a start-up.“

DadHacker

APC update (3.1.4) – configuration notice

August 11th, 2010

APC finally follows the standard of using suffixed values for memory sizes specified inside your php.ini (or APC’s dedicated ini). So if you encounter a

PHP Warning: PHP Startup: apc.shm_size now uses M/G suffixes, please update your ini files

while still having something like (e.g. in /etc/php.d/apc.ini)

; The size of each shared memory segment in MB.
apc.shm_size=512

in your configuration, its enough to append the respective unit indicator (M = Mega, G = Giga) to the number in order to update your configuration to comply with the requirements.

apc.shm_size=512M

tagesschau.de feat. forium.de

April 16th, 2010
tagesschau.de IP 213.203.237.130 213.203.237.130

inetnum:         213.203.237.128 - 213.203.237.131
netname:         DE-FORIUM-TRANSFER
descr:           forium GmbH
...
address:         Kantstraße 13
address:         10623 Berlin

It’s up to Jerry Fletcher to connect the dots.

happy easter — debugging

April 5th, 2010

At the moment gearman(d) keeps me occupied at work. I am soon going to give (yes, yet another) deeper insight into that.

Aside of the obvious, my first findings boil down to the following

  • When running PHP workers, don’t even try to make them stay alive forever.  Have them commit suicide (sounds dirty but has the advantage that the process itsself knows when its idle) and be reborn on a regular basis. Saves a lot of hassle.
  • Never do the mistake, even if it seems sufficient, to only have one PHP worker running for each gearman server. I had three servers on three individual physical machines, running with one worker each, and all hell rained down (did you ever happen to see a load 500?).

amazon character set struggle?!

März 7th, 2010

Stubled upon the Amazon search form and got curious about some seemingly useless hidden form value which is always equally set…

<form ... >
<input value="ÅMÅZÕÑ" name="__mk_de_DE" type="hidden" />
...

The only use I could make up for it would be (a really ingenious approach) that the receiving script could, by knowing what is supposed to be the value of this field, try to find issues in the transfered form encoding, so an automatic sanitation of the actually interesting part of the query – the search term – could be performed.

Boy, are they clever…