As I recall, you can find the default value for
package_list_update_ifelapsed in the Cfengine standard library.
Aleksey
On Fri, Jul 22, 2011 at 6:39 AM, Sjoerd Oostdijck wrote:
> Hi Sven,
>
> I had similar strange behavior with yum and the caching of installed
> packages. I worked around it by
Hi Sven,
I had similar strange behavior with yum and the caching of installed
packages. I worked around it by creating my own version of yum_rpm and
adding in:
package_list_update_ifelapsed => "1";
That'll at least force things to update the cache... Who knows how long
it caches by default.
On
Forum: CFEngine Help
Subject: Re: CFEngine Help: Re: yum_rpm automatic package upgrades
Author: svenXY
Link to topic: https://cfengine.com/forum/read.php?3,22876,22879#msg-22879
Unfortunately, no. I think I set the update interval to 1 and also used -K and
also tried this a couple of times. I&#
I haven't played with this aspect of Cfengine yet, but I do know that
Cfengine caches yum output to reduce its resource footprint. Could it
be Cfengine cached v24 and then v26 became available at the repo but
Cfengine is still looking at its cache where it sees v24 as the latest
version? Just a w
Forum: CFEngine Help
Subject: Re: yum_rpm automatic package upgrades
Author: svenXY
Link to topic: https://cfengine.com/forum/read.php?3,22812,22820#msg-22820
nobody?
Is this so uncommon?
Furthermore, this fails also:
vars:
"old_java_rpm" string => "1.6.0_24-fcs";
some_class::
"jdk"
