[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: [K12OSN] yum.cron question
- From: Henry Hartley <henryhartley westat com>
- To: "'Support list for opensource software in schools.'" <k12osn redhat com>
- Subject: RE: [K12OSN] yum.cron question
- Date: Thu, 13 Jan 2005 12:11:05 -0500
>> -----Original Message-----
>> From: Calvin Dodge
>> Sent: Thursday, January 13, 2005 12:03 PM
>>
>> On Thu, Jan 13, 2005 at 11:04:59AM -0500, Henry Hartley wrote:
>> > In /etc/cron.daily/yum.cron, I have the following:
>> >
>> That lock isn't set by yum. It's set by "/etc/init.d/yum start",
>> since it's a flag to tell yum "do updates", rather than a lock telling
>> yum "another instance is running".
>>
>> Look at the first 25 lines of /etc/init.d/yum, and all will become
>> clear.
Ah, yes, now I see.
>> Meanwhile, yum may have hung. Do a "ps auxww|grep yum". If you see a
>> yum process there (usually starting with "/usr/bin/python") kill it,
>> then try running yum manually to catch up with the latest security
>> updates.
The problem was that the there was no symlink in /etc/rc.d/rc3.d to the yum
script. Without that, there was no /var/lock/subsys/yum and the cron job
just did nothing (as it was intended). I suppose that's a reasonable
default. I manually ran "yum update" to get caught up, ran "/etc/init.d/yum
start" and created a S98yum symlink. Thanks for your time.
--
Henry
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]