using the Yum Installation Schedule Task feature, the result is:
Copy Code
The code is as follows:
# yum-y Install Vixie-cron
Loaded Plugins:fastestmirror, Refresh-packagekit, security
Existing lock/var/run/yum.pid:another copy is running as PID 25960.
Another app is currently holding the Yum lock; Waiting for it to exit ...
It is possible that the system auto upgrade is running and the Yum is in a locked state.
There's already a Yum process running, killing it with a kill:
Copy Code
The code is as follows:
# kill-s 9 25960
# PS Aux|grep Yum
Root 6744 0.0 0.0 103260 900 PTS/1 s+ 14:59 0:00 grep yum
Root 25960 0.0 0.0 0 0? Z Sep19 0:01 [yumbackend.py]
It is a pity that kill can't deal with it, then how to do?
You can disable the Yum process by forcing:
#rm-F/var/run/yum.pid
Then you can use the Yum. If not, you can restart Yum.
/sbin/service yum-updatesd Restart
This is supplemented by other netizens:
Add one,
Sometimes, under Linux yum update prompts:
Another app is currently holding the Yum Lock solution
The solution is to kill the Yum process in the cache and reboot the Yum.
To clear the process in the cache:
Rm-f/var/run/yum.pid
Reboot Yum (my system is fedora)
Systemctl Status Yum-updatesd.service
CentOS users use:
/sbin/service yum-updatesd Restart
Add two,
An error occurred while yum-y install gcc* gcc-c++* autoconf* automake* zlib* libxml* ncurses-devel* libmcrypt* libtool* on CentOS:
1 What's going on? As prompted, the system process already has an update running. In the process view under: Ps-ef | grep update
2 Kill the process by killing, but after killing, the error remains. Originally in the/var/run directory, and Yum This process ID, you need to force the process ID file to delete:
3) At the same time restart the Yum update Service, as follows:
4) Finally yum-y install gcc* gcc-c++* autoconf* automake* zlib*, libxml* ncurses-devel* libmcrypt* libtool*, Normal