On Fri, May 28, 2010 at 12:27 PM, George R Goffe <span dir="ltr"><<a href="mailto:grgoffe@yahoo.com">grgoffe@yahoo.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font:inherit">Tim,<br><br>I have been looking for replies but found none, that is why I re-posted. In looking at the archive I see that some have not arrived in my inbox. Sigh. I have been having troubles with yahoo classic for the past few months, searching fails randomly, filters disappear randomly, sorting of email fails intermittently, numerous error codes (2,3,4,5,6,20,22) and the winner, "an error has occurred". I know, it's hard to believe that last one. Their support structure is in need of serious help.<br>
<br>Anyway. I run "yum update" every other day and then yum clean all which always reports 0 pkgs removed. I'm probably doing something wrong but for the life of me, I can't see it. Maybe a plugin?<br><span class="Apple-style-span" style="font-size: small;"><span class="Apple-style-span" style="font-size: medium;"><br>
</span></span></td></tr></tbody></table></blockquote><div><br></div><div>Have a look at /etc/yum.conf and see if you have a line:</div><div> keepcache=1</div><div><br></div><div>If this is the case then it keeps the package rpms in cache - if the parameter is zero then it does not keep the rpms in cache and so yum clean all will have no packages to remove!</div>
<div><br></div><div>The default is zero.</div><div><br></div><div>This may explain your observations and for most people there is no need to clog up your system partition with the stored rpms. If you want to copy the rpms to another machine without the need to download again then you may want keepcache=1 and then transfer the rpms locally to the other machine and then run yum update on that machine which itself will then not need keepcache=0</div>
<div><br></div><div>Mike</div></div>-- <br>mike c<br>