Page MenuHomeDevCentral

Handle .geoipupdate lock file
ClosedPublic

Authored by dereckson on Mar 16 2023, 19:14.
Tags
None
Referenced Files
F12298115: D2902.diff
Mon, Oct 20, 14:04
Unknown Object (File)
Mon, Oct 20, 07:02
Unknown Object (File)
Mon, Oct 20, 06:54
Unknown Object (File)
Mon, Oct 20, 06:53
Unknown Object (File)
Mon, Oct 20, 06:48
Unknown Object (File)
Sat, Oct 18, 08:34
Unknown Object (File)
Sat, Oct 18, 05:18
Unknown Object (File)
Sat, Oct 18, 03:16
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.