diff options
author | Chantry Xavier <shiningxc@gmail.com> | 2007-09-08 00:36:38 +0200 |
---|---|---|
committer | Dan McGee <dan@archlinux.org> | 2007-09-16 20:17:44 -0500 |
commit | b0aa51059233849b0a7ef8d6a851750776ce6645 (patch) | |
tree | 29341593cb82011f65e901aa63bc76f7449d85a2 /pactest/tests/sync895.py | |
parent | 046c8a6819a0533fb10434f30100f80bb960fe46 (diff) |
trans.c : reworking of transaction interruptions
My two previous hacks related to this part
(8038190c7c4786e1c49494eea1b40cdddcbd5136 and
b15a5194d1a8485a2769560e49e6ff03e1862533) were caused by the lack of
understanding of a feature introduced a while ago:
Better control over CTRL-C interruptions -- do not leave the DB in an
inconsistent state (54008798efcc9646f622f6b052ecd83281d57cda).
Now I have been looking at this commit, and the added feature is indeed
interesting. The main problem I had with it is that it does a rather
unusual use of alpm_trans_release, which caused a few problems that I tried
to fix in a weird way. I think these problems were caused by the fact that
there weren't any difference between "interrupt transaction" and "release a
transaction which failed" actions from the alpm_trans_release POV. So I
decided to add a new function instead, alpm_trans_interrupt, which is
called on Ctrl+C, and which only sets trans->state to STATE_INTERRUPTED so
that remove_commit and add_commit can exit cleanly at a safe moment. This
allowed me to revert my two previous hacks as well.
Also ensure we handle SIGINT correctly in all cases- if a transaction is
not ongoing, then we can free the transaction and exit quickly.
Signed-off-by: Chantry Xavier <shiningxc@gmail.com>
Signed-off-by: Dan McGee <dan@archlinux.org>
Diffstat (limited to 'pactest/tests/sync895.py')
0 files changed, 0 insertions, 0 deletions