Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

YUM Config?

Status
Not open for further replies.

JohnPtrs

MIS
Jun 13, 2006
91
US
I have configured my /etc/yum.conf file to point to the server I want it to get updates from, however when I run etherape I can see that it seems to be getting updates from multiple other servers even though the one I want is the only one in my conf file... Anybody have any ideas why? I hope its not something stupid HA HA... Below is my yum.conf ... Thanks!

[main]
cachedir=/var/cache/yum
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
metadata_expire=1800

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

#Base
baseurl=ftp://limestone.uoregon.edu/fedora/5/i386/os/

#Updates
baseurl=ftp://limestone.uoregon.edu/fedora/updates/5/i386/
 
More than likely you have items still in here:
Code:
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
that were part of the default install from RH/fedora.

Kill those off and yum should behave as expected.

D.E.R. Management - IT Project Management Consulting
 
You're the man!! That was the issue, I had to clear those out and add the server I wanted to those repo files to make it work... can't it just be made to use the yum.conf file instead of using the repo files?

JP
 
It appears to me that yum is compiled with a parameter "resposdir" which has a default value of "yum.repos.d". I looked in my /etc/init.d/yum folder to see if I could get any clues from it whether there's an over-ride to "null". I also googled and checked the man pages.

I believe the only approach available to you without extensive effort is to simply remove the repos files from the "yum.repos.d" folder and perhaps consider either removing the folder itself, or making the folder chmod 700 and chown root.root

What I don't know is how loudly yum will complain when this folder is empty, non-accessible, missing, etc.

Probably the only risk of purging off the repos files is that they might come back when yum updates yum itself from a repos.

D.E.R. Management - IT Project Management Consulting
 
Thanks for the input... yesterday I had renamed the repo files to repo.old thinking it may then look to the /etc/yum.conf however when I tried to update it simply said it had no servers to check... either way it is working now as is... Thanks again...

JP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top