Andre Hinrichs <[EMAIL PROTECTED]> writes: > 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.
... and some overhead each time the client starts and loosing the benefits of forked upload. If you want to restart the client without killing it first you can do "touch tilesGen.pl". The client restarts itself when it detects that this file has changed. The test for a changed config file is somewhere on my todo list. Your other issues need to be looked after. There are probably more inconsistencies and glitches in the client's behavior. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
