| 1 |
>>>>> On Thu, 11 Nov 2021, Ulrich Mueller wrote: |
| 2 |
|
| 3 |
> In any case, we have run out of GIDs: |
| 4 |
|
| 5 |
> Recommended GID only: none |
| 6 |
> Recommended UID only: 272 |
| 7 |
> Recommended UID+GID pair: none |
| 8 |
> Free UIDs: 15 |
| 9 |
> Free GIDs: 0 |
| 10 |
> Free UID+GID pairs: 0 |
| 11 |
|
| 12 |
> The question is of course how we should move forward. Certainly, using |
| 13 |
> IDs below 100 cannot be the solution, as we would run out of these very |
| 14 |
> soon. |
| 15 |
|
| 16 |
> We could: |
| 17 |
|
| 18 |
> - Open some part of the range between 500 and 1000. For example, |
| 19 |
> 500..799, which would leave 200 IDs for dynamic allocation. |
| 20 |
|
| 21 |
> - Open part of the range 60001..65533. Not sure if all software will be |
| 22 |
> happy with that. |
| 23 |
|
| 24 |
> - Admit that the concept of static allocation has failed, and return to |
| 25 |
> dynamic allocation. |
| 26 |
|
| 27 |
By today's council decision, the whole range from 101 to 749 is now |
| 28 |
available. The used_free_uidgids.sh script has been updated accordingly. |
| 29 |
|
| 30 |
There seem to be some issues with system IDs above 60000 especially with |
| 31 |
systemd. We'll try to sort these out before we run out of IDs again. |
| 32 |
|
| 33 |
Ulrich |
Archives