--no-warn-on-lock doesn't work

[GoogleCodeExporter]

It seems that --no-warn-on-lock doesn't work in YUM versions of RHEL 5 and 6.

Original issue reported on code.google.com by [email protected] on 13 Sep 2012 at 11:09

[GoogleCodeExporter]

The reason seems to be that YUM itself never exits when another instance of it 
has the lock, but rather waits infinitely for the lock to be released.

Eventually check_yum runs into its timeout then.

Original comment by [email protected] on 13 Sep 2012 at 11:23

• Changed state: New

[GoogleCodeExporter]

I started a thread on yum-devel about this:
http://lists.baseurl.org/pipermail/yum-devel/2012-September/009641.html

Likely I'll drop the current (non-working) code from check_yum and just add 
exit_on_lock = true .


This will however only work in newer yum versions.... maybe I'll add some code 
to support olders, too,... will see.

Original comment by [email protected] on 27 Sep 2012 at 11:26

• Changed state: Started

[GoogleCodeExporter]

Reported:
https://bugzilla.redhat.com/show_bug.cgi?id=861250
https://bugzilla.redhat.com/show_bug.cgi?id=861251
asking for exit_on_lock to be backported to RHEL 5 and 6.

Original comment by [email protected] on 27 Sep 2012 at 11:37

[GoogleCodeExporter]

RHEL6 already has exit_on_lock (--setopt=exit_on_lock=true) - Is a release 
(v1.0.1) coming - which uses this, if the yum version is new enough?

Original comment by [email protected] on 1 Jul 2013 at 10:59

[GoogleCodeExporter]

yum v3.2.29 (el6) has support. yum v3.2.22 (el5) does not.

Original comment by [email protected] on 1 Jul 2013 at 11:04

[GoogleCodeExporter]

Hi.

I know about the support for --setopt=exit_on_lock=true, actually I lobbied RH 
for backporting it to RH6 ;-)

But to be honest, I'm very busy with other stuff right now (and probably for 
quite some time)... so it's uncertain when I have more time again to take care 
on check_yum... so (clean) patches would be welcomed.

Cheers,
Chris.

Original comment by [email protected] on 1 Jul 2013 at 11:19