Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# lsb_release -a
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.5 (Final)
Release: 6.5
Codename: Final
yum automatically installs upgrade. I would like to do this manually, instead.
I did not set any crontab or similar.
Where can I find the origin of this behavior?
Thankyou
That would probably be the package yum-cron. You could simply uninstall it, or check `man yum-cron` for ways to control it. You can see the files involved by running "rpm -ql yum-cron".
This is for ScientificLinux instead
BUT
the same applies
if YOU !!! want to determine WHEN the "upgrade" is ran
( i do this )
make SURE that the repos are using 6.4
then upgrade to 6.5
the next in about 6 to 8 months it to 6.6
Code:
--- code--- 6.5/$basearch/os/
---------- this is for SL 6.5 ! you will need to edit YOUR files
baseurl=http://ftp.scientificlinux.org/linux/scientific/$releasever/$basearch/os/
http://ftp1.scientificlinux.org/linux/scientific/$releasever/$basearch/os/
http://ftp2.scientificlinux.org/linux/scientific/$releasever/$basearch/os/
ftp://ftp.scientificlinux.org/linux/scientific/$releasever/$basearch/os/
#mirrorlist=http://ftp.scientificlinux.org/linux/scientific/mirrorlist/sl-base-6.txt
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-sl file:///etc/pki/rpm-gpg/RPM-GPG-KEY-sl6 file:///etc/pki/rpm-gpg/RPM-GPG-KEY-cern
It is unclear which of two scenarios is the basis of your complaint:
I ran "yum update" and it unexpectedly upgraded my system to the latest point release.
yum ran automatically and upgraded my system without any action by me.
For case (1), that is normal behavior for CentOS. If you believe that you want to stay locked at, for example, release 6.4, you can substitute that for "$releasever" in the .repo file, but be warned that release 6.4 receives no more updates after 6.5 becomes available.
For case (2), there must be something in /etc/cron.{hourly,daily,weekly,monthly} or /var/spool/cron that is doing the update.
It is unclear which of two scenarios is the basis of your complaint:
I ran "yum update" and it unexpectedly upgraded my system to the latest point release.
yum ran automatically and upgraded my system without any action by me.
For case (1), that is normal behavior for CentOS. If you believe that you want to stay locked at, for example, release 6.4, you can substitute that for "$releasever" in the .repo file, but be warned that release 6.4 receives no more updates after 6.5 becomes available.
For case (2), there must be something in /etc/cron.{hourly,daily,weekly,monthly} or /var/spool/cron that is doing the update.
# yes sets yum to check for updates and mail only if patches are available
# no does enable autoupdate if /var/lock/subsys/yum is available
CHECKONLY="yes"
# defaults to root, leave empty if .forward/alias in place for root
MAILTO="myemail@domain.net"
# Set to yes for debugging only! You'll get a mail for each run!
CHECKWRK="no"
# Seconds to randomize startup, if running from cron to balance load
RANGE="3600"
so, as CHECKONLY=yes, I can't explain why my system updates itself.
Thank you
Where did the "yum-check" executable and config file come from? I can't find any package for CentOS that would provide those. Output from "ls -l /usr/bin/yum-check" and "rpm -qif /usr/bin/yum-check /etc/sysconfig/yum-check" would be useful.
Where did the "yum-check" executable and config file come from? I can't find any package for CentOS that would provide those. Output from "ls -l /usr/bin/yum-check" and "rpm -qif /usr/bin/yum-check /etc/sysconfig/yum-check" would be useful.
Another possibility, if this machine was an upgrade from CentOS 5, would be a leftover yum-updatesd package (no longer provided in CentOS 6). File /etc/yum/yum-updatesd.conf would be the config file for that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.