Page MenuHomeDevCentral

Handle .geoipupdate lock file
ClosedPublic

Authored by dereckson on Mar 16 2023, 19:14.
Tags
None
Referenced Files
F24668455: D2902.diff
Wed, Mar 4, 06:42
F24666995: D2902.id7397.diff
Wed, Mar 4, 05:01
F24666987: D2902.id7396.diff
Wed, Mar 4, 05:00
F24663676: D2902.diff
Tue, Mar 3, 23:51
Unknown Object (File)
Sun, Mar 1, 11:16
Unknown Object (File)
Mon, Feb 23, 10:00
Unknown Object (File)
Fri, Feb 13, 00:33
Unknown Object (File)
Wed, Feb 11, 06:41
Subscribers
None

Details

Summary

The geoipupdate client creates a lockfile to avoid race conditions.

Drawbacks of the current method is:

  • no lock file created at first run
  • can be confusing to see it afterwards

To address both those concerns, the wrapper creates and deletes
this lock file before and after the container run.

Reference: https://github.com/maxmind/geoipupdate-legacy/issues/79

Test Plan

Tested on docker-002

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Mar 16 2023, 19:15
This revision was automatically updated to reflect the committed changes.