Re: control-C and yum update
On Sun, 2010-01-03 at 21:42 -0800, Paul Allen Newell wrote: While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. In the yum updating case, it's breaking the current process (downloading some file), but not the thing controlling it. You'd need to CTRL+C more than once, to break the chain of events higher up. The first break will abort the current download, and yum will try to download the same file from another repo, as the next action. This is actually useful, for things like when you notice the download is excruciatingly slow, but you still want to do a yum update. You can simply CTRL+C to make it use another repo mirror. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
On 10-01-05 03:01:45, Tim wrote: ... In the yum updating case, it's breaking the current process (downloading some file), but not the thing controlling it. You'd need to CTRL+C more than once, to break the chain of events higher up. ... No, yum is doing the download in-process. It takes two Ctrl-C's to quit during download so one can switch mirrors with one Ctrl-C. Yum is getting both of them and counting and timing them to decide what to do. The approach I took in my stablemirror yum plugin is to show a short menu of commands and let the user choose one, rather than count and time them. Either way works, but my way offers more choices. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. pgpvWl9093Y1T.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
On Mon, 2010-01-04 at 07:14 -0500, Sam Varshavchik wrote: Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines I have been using Tony Nelson's stablemirror for several years (and Control/C) with yum (currently F12) with no problems. http://www.georgeanelson.com/stablemirror.htm Stablemirror provides working Ctl-C handling during downloads, in a way that I belive is safe for the underlying RPM database. John -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
On 04/01/2010 12:14, Sam Varshavchik wrote: Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. You have to hit Crtl-C twice! not just the once, and within' five seconds of each other -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
On 10-01-04 08:12:39, John Austin wrote: ... I have been using Tony Nelson's stablemirror for several years (and Control/C) with yum (currently F12) with no problems. http://www.georgeanelson.com/stablemirror.htm Stablemirror provides working Ctl-C handling during downloads, in a way that I belive is safe for the underlying RPM database. I am /astounded/ that it hadn't stopped working with all the changes to yum since 2007. I hadn't been using it myself, as both the mirrors and yum have seen improvement over time, but I did occasionally miss it. I've installed it again and will look for any problems it might have with current yum. Anyone choosing to use stablemirror will probably want to disable fastestmirror. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
2010/1/4 Paul Allen Newell pnew...@cs.cmu.edu: I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. It's an interrupt, which could be blocked or it might be on a different queue. You should be able to background yum and kill it straight away: Ctrl+z kill %1 -c -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: control-C and yum update
Chris Smart wrote: 2010/1/4 Paul Allen Newell pnew...@cs.cmu.edu: I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. It's an interrupt, which could be blocked or it might be on a different queue. You should be able to background yum and kill it straight away: Ctrl+z kill %1 -c Chris: Got it ... this makes sense as there are jobs I run that I have to ps and then kill. If yum blocks until first y/N, it makes sense. Thanks, Paul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
