I know this has been discussed lots before, but the discussions before centered on interactive yum use. [root@box ~]# yum install rdesktop Loading "presto" plugin Loading "installonlyn" plugin Loading "fastestmirror" plugin Loading "protectbase" plugin Setting up Presto Reading Presto metadata in from local files Loading mirror speeds from cached hostfile Existing lock /var/run/yum.pid: another copy is running as pid 2763. Aborting. [root@box ~]# kill 2763 [root@box ~]# yum install rdesktop Loading "presto" plugin Loading "installonlyn" plugin Loading "fastestmirror" plugin Loading "protectbase" plugin Setting up Presto Reading Presto metadata in from local files Loading mirror speeds from cached hostfile Existing lock /var/run/yum.pid: another copy is running as pid 2763. Aborting. Sending a kill command to a program should make the program quit.
not if the program (or in this case a library the program is using) has grabbed the sigterm signal handler and refuses to obey it. You have to kill -9 it b/c of the grab by rpm of the signal handler. to be fair - in certain situations this is desired behavior. During the transaction, for example, I think it would be wise to make the user REALLY want to stop the yum process by using a kill -9 b/c during various portions of the transaction stopping the process can leave you with an unstable or completely broken system.
Created attachment 159642 [details] Make yum listen to signals Attached patch, together with rpm-4.4.2.1-0.5.rc3 (in next rawhide push) makes yum check for signals caught by rpm during downloads if the rpm version supports it. There might be other places where the checking is needed but this takes care of the worst part.
applied the patch to cvs. Should be out in next release