[Tilesathome] either nodata or Forked render failure

[Sebastian Spaeth]

Florian Lohoff wrote:
> Hi,
> it seems somethings still essentially broken - Currently all requests
> either produce a NoData or a Forked render failure - It seems there are no
> requests successfully processed ...

There is nothing at all I can do about the NoData thing. It really seems 
to be the API that aborts downloads. Often seconds after trying which is 
crazy.

The Forked Render Failure was an icky tricky bug that I have under 
control now. (as of r10185)

Basically, whenever a child thread was exiting, it was calling the 
destuctor method "DESTROY" of the Tileset object (which it is not 
supposed to do). So whenever a child thread finished rendering to svg it 
would delete the temporary job directory. I protect against that now. 
And forking should actually work again now. I disable the forking for 
inkscape for now (I need to examine that code closely first), but 
xml2svg and the beziercurving should actually work now.

I am still testing the new code on my (rather oldish) box and will then 
update the client version, so everyone picks up the latest stuff.

For now you are still on the save side if you disable forking with 
Fork=0 in your tilesAthome.conf

>   The following command produced an error message:
>   nice -n10 perl orp/orp.pl -r /home/flo/tah/tilestmp1/12_2121_1374_uiWwM/map-features-z17.xml -o /home/flo/tah/tilestmp1/12_2121_1374_uiWwM/output-z17.svg-temp.svg
>   Debug output follows:
>   | Can't call method "close" on an undefined value at orp/orp.pl line 487.

What SVN revision of or/p do you have in your directory? I don't see how
$output->close() can be undefined when you clearly have the output 
specified with "-o 
/home/flo/tah/tilestmp1/12_2121_1374_uiWwM/output-z17.svg-temp.svg"

I don't know or/p well enough to be able to say what's going on there.

spaetz