| 1 |
On 5/11/20 10:54 PM, Michał Górny wrote: |
| 2 |
> W dniu nie, 10.05.2020 o godzinie 21∶32 -0700, użytkownik Zac Medico |
| 3 |
> napisał: |
| 4 |
>> The feature enables finer grained locks for install operations, and |
| 5 |
>> everyone agrees that it's safe to enable by default. |
| 6 |
> |
| 7 |
> Who's 'everyone' and where's their analysis of the problem? |
| 8 |
> The manpage doesn't really help understand what this does, exactly. |
| 9 |
|
| 10 |
Before parallel-install there was just one big lock, so only one package |
| 11 |
slot could enter the merge/unmerge state at a given time. |
| 12 |
|
| 13 |
With parallel install, there are a few finer-grained locks that come |
| 14 |
into play. These are the really important ones: |
| 15 |
|
| 16 |
* When merging/unmerging files, an exclusive lock must be held on |
| 17 |
vardbapi._fs_lock. |
| 18 |
|
| 19 |
* When executing an unsandboxed ebuild phase, an exclusive lock must be |
| 20 |
held on the FEATURES=ebuild-locks lock. |
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Zac |
Archives