Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • pw-autocomplete-off
  • redis-rate-limits
  • typehints
  • incremental-sync
  • test_instance_path
  • consistent_strings
  • qol_edits
  • v1.2.x
  • v1.x.x
  • v1.1.x
  • feature_invite_validuntil_minmax
  • Dockerfile
  • pylint_disable_consider-using-f-string
  • v1.0.x
  • roles-recursive-cte
  • v2.2.0
  • v2.1.0
  • v2.0.1
  • v2.0.0
  • v1.2.0
  • v1.1.2
  • v1.1.1
  • v1.0.2
  • v1.1.0
  • v1.0.1
  • v1.0.0
  • v0.3.0
  • v0.2.0
  • v0.1.5
  • v0.1.4
  • v0.1.2
32 results

uffd

  • Clone with SSH
  • Clone with HTTPS
  • Forked from uffd / uffd
    Source project has a limited visibility.
    Julian Rother's avatar
    Julian authored
    Previously Unix UIDs/GIDs were allocated by using the highest used ID + 1.
    This caused ID reuse when the newest user/group was deleted. In addition, the
    implementation did not work on MariaDB (at all, it was not possible to create
    users/groups).
    
    The new approach accounts for all IDs ever used regardless of whether or not
    users/groups are deleted. It always allocates the lowest ID in the configured
    range that was never used.
    
    Aside from the different allocation algorithm, this change introduces a
    generic locking mechanism and prerequisites for testing migration scripts.
    53c06069
    History
    Name Last commit Last update