Issues with yum

[Panu Matilainen]

On 02/27/2012 06:00 PM, John Reiser wrote:
> On 02/27/2012 07:29 AM, Bruno Wolff III wrote:
>> On Mon, Feb 27, 2012 at 14:00:51 +0000,
>>    Frank Murphy<frankly3d at gmail.com>  wrote:
>>> On 27/02/12 13:52, elison.niven at gmail.com wrote:
>>>>
>>>> 4) Quit on single CTRL-C. Users expect an application to quit on
>>>> pressing CTRL-C.
>>>> Reason to have this feature : Better user experience
>>>
>>> never used ctrl-c, normally use "killall yum"
>>> if required.
>>
>> Control C works, but it needs to reach a break point. And once you start
>> actually doing a transaction you don't normally want control C to work
>> since it will leave your system in a state where manual cleanup is likely
>> required.
>
> That behavior (no response to ^C [SIGINT] within 5 seconds) is a bug.
> It's a _transaction_, right?  So either it completes successfully,
> or fails with no apparent lasting effects (except log files, delay, etc.)
> So yum should: respond immediately on stderr, abort the transaction
> (roll back everything to the state before the transaction began),
> and terminate with failure status.  Because the original request
> is for a transaction, then yum *must* be able to abort and rollback
> anyway, to recover from I/O errors [and such errors _do_ happen.]
> So, act as if ^C [SIGINT] is an I/O error.

Rpm's so-called transactions aren't ACID by any stretch of imagination, 
it's just a rather common misunderstanding to expect them to be.

	- Panu -