ken wrote:
> On 08/03/2010 06:52 AM John Doe wrote:
>> From: ken <gebser@xxxxxxxxxxxx>
>>> ....
<snip>
> Trying again: it's happened to me a few times now that when I run "yum
> update", it fails like this:
>
> The other application is: yum-updatesd-he
> Memory : 31 M RSS ( 74 MB VSZ)
> Started: Tue Aug 3 04:40:05 2010 - 1:25:42 ago
> State : Running, pid: 32006
> Another app is currently holding the yum lock; waiting for it to exit...
> The other application is: yum-updatesd-he
> Memory : 31 M RSS ( 74 MB VSZ)
> Started: Tue Aug 3 04:40:05 2010 - 1:25:44 ago
> State : Running, pid: 32006
<snip>
> # ps -ef|grep yum
> root 864 3195 0 06:06 pts/1 00:00:00 grep yum
> root 2632 1 0 Jul27 ? 00:05:13 /usr/bin/python -tt
> /usr/sbin/yum-updatesd
> root 32006 2632 1 04:40 ? 00:00:54 /usr/bin/python -tt
> /usr/libexec/yum-updatesd-helper --check --dbus
>
> After killing 32006, then 2632, "yum update" ran fine. (Perhaps I
> didn't need to kill the second one... 2632. Dunno.)
Yep - if any version of yum is running, no other will. At work, I do *not*
have yum-updatesd turned up - I want to control when and what. Certainly,
I don't want to update, say, firefox while folks are using it on their
desktops. And some managers are rather picky as to what servers get
updated, and when, esp. their production boxes. So, it's tedious, but I
have control - yum runs when I run it, and not otherwise.
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
