[Tilesathome] Some questions on client behaviour

[Andre Hinrichs]

Hi List,

I've some questions (and maybe suggestions) to the client developers.

1.) Why is the client sleeping for 60 seconds when rendering is finished and 
the client is not in loop mode?

2.) Why is the client sleeping for 60 seconds before getting a new job when 
the server upload queue is too full? Isn't sleeping before uploading the 
rendered tiles enough?

3.) Why is the client getting a new job after case 3.) even if there is a 
stopfile?

4.) Why do I have to start a separate upload process after rendering when the 
client is not in loop mode?

Suggestion to 1.) Implementation of a "batch mode" where this sleep is 
skipped. This would help me a bit, since I wrote a small bash script which is 
checking a central stopfile so that I only have to set the stopfile once for 
all clients. (You can find the script at the end of this mail.) 

Suggestion to 4.) Implementation of a new option to do rending and uploading 
in one step. Normally I would have expected that this is the default but 
changing the behavior now could probably cause problems with some other 
control scripts.

Comments to the script below: Advantage is that changes to the 
tilesAtHome.conf are taken automatically when the next renderer is started. 
Disadvantage is that the complexity calculation is out of order then.


Regards
Andre

--- script start ---
#!/bin/bash

while [ -d /osm/tah -a ! -f /osm/tah/stopfile.txt ]; do
    if [ -f /osm/tah/sleep.txt ]; then
        echo "/osm/tah/sleep.txt found. Start of renderer skipped and sleeping 
for 60 seconds."
        sleep 60
    else
        perl tilesGen.pl
        [ $? -eq 0 ] && perl tilesGen.pl upload
    fi
done

# End
--- script end ---