Hi Thomas, Thanks for the response & explanation. Makes sense.
thomas bonfort wrote > Given Matthew's usecase, I also suspect that restarting apache is not > an acceptable behavior. You'd be right. At certain times of the day, depending on data arrival, we could be running > 1 concurrent seeding processes, and also allowing live users to seed any tiles on the fly. For the most part, it works (although it pollutes the logs a fair bit). Sometimes it doesn't work, but the worst case scenario here is that the next attempt to load that tile, it will get created and served to the live user. For now, we are happy to live with option 1 - live with the risk of tile corruptions and/or missed tiles. We have configured OpenLayers IMAGE_RELOAD_ATTEMPTS to re-request up to three times, if a request for a tile fails, so the chance of the user seeing dead tiles is greatly reduced. Regards, Matt -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Lock-file-limit-on-many-concurrent-seeding-processes-SEC-UNCLASSIFIED-tp5034835p5037422.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
