[MapProxy] Lock files in 1.8.0

[Oliver Tonnhofer]

Hi,

that does look like a bug!

We need to find the root-cause of that issue to be able to create a fix. It’s easy if we can reproduce a bug, it’s really hard if we can’t. In order to reproduce this bug, we need as much information as you can provide:
 
- Which platform do you use (Windows X, Foobuntu Linux, etc)?
- Which Python version do you use?
- Which package versions of MapProxy and dependencies do you use?
- Does the bug show up with `mapproxy-util serve-develop`, or only in full deployment?
- What deployment do you use (Apache mod_wsgi, etc.)?
- Can you provide a minimal configuration that triggers this bug?
- What requests do you make (WMS, WMTS, etc.)? Can you provide URLs of example requests?



Regards,
Oliver

-- 
Oliver Tonnhofer  | Omniscale GmbH & Co KG  | http://omniscale.com
OpenStreetMap WMS and tile services         | http://maps.omniscale.com




> On 27.07.2015, at 17:08, Petróczki Imre <petroczkiimre at gmail.com> wrote:
> 
> Hi,
> 
> I have two servers with the same mapproxy configuration. The only
> difference is that the first server runs mapproxy 1.7.1 while the
> second runs 1.8.0
> I noticed that the tile locking mechanism has changed in 1.8.0. I have
> thousands of lock files but the mapproxy doesn't delete them. Some of
> them are 3 weeks old. I have never experienced this with 1.7.1.
> 
> Thank you very much in advance for your help.
> 
> Regards,
> Imre Petróczki
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapproxy