summaryrefslogtreecommitdiff
path: root/doc/en
diff options
context:
space:
mode:
authorDaniel Burrows <dburrows@debian.org>2009-10-26 15:25:34 -0700
committerDaniel Burrows <dburrows@debian.org>2009-10-26 15:25:34 -0700
commit509e223501b2240a351cab26565ec3c9cf4aba72 (patch)
tree5556c004de758e740047c92b0982416fc7380bdd /doc/en
parent72fe14fa6b093d8773d019941c0f24f33e217eba (diff)
downloadaptitude-509e223501b2240a351cab26565ec3c9cf4aba72.tar.gz
Get rid of get_solution_background_blocking.
Now that the resolver continuations run in the foreground thread, this was causing irreconcilable deadlocks (since the foreground thread would be waiting for someone to post the return result, which could only happen when the foreground thread finished running the continuation and polled for new posted thunks).
Diffstat (limited to 'doc/en')
-rw-r--r--doc/en/aptitude.xml13
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/en/aptitude.xml b/doc/en/aptitude.xml
index 00d6432d..c3478487 100644
--- a/doc/en/aptitude.xml
+++ b/doc/en/aptitude.xml
@@ -11500,19 +11500,6 @@ e: Examine !: Apply .: Next ,: Previous</screen>
</seg>
</seglistitem>
- <seglistitem id='configProblemResolver-WaitSteps'>
- <seg><literal>Aptitude::ProblemResolver::WaitSteps</literal></seg>
- <seg><literal>50</literal></seg>
- <seg>
- The number of resolver steps to perform in the
- foreground before moving the resolution to the
- background thread. &aptitude; will be unresponsive
- while this computation takes place; decreasing this
- value will make the program more responsive, but may
- cause the progress indicator to appear unnecessarily.
- </seg>
- </seglistitem>
-
<seglistitem id='configPurge-Unused'>
<seg><literal>Aptitude::Purge-Unused</literal></seg>
<seg><literal>false</literal></seg>