Re: [Spacewalk-list] server says client should be updated, but nothing happens

: Re: [Spacewalk-list] server says client should be updated, but nothing happens Thanks, but that sounds like a hack. I would think this sort of scheduling would be a pretty common feature request . . . anyone know if this will ever be implemented in spacewalk, or if it's been turned down

Re: [Spacewalk-list] server says client should be updated, but nothing happens

Thanks, but that sounds like a hack. I would think this sort of scheduling would be a pretty common feature request . . . anyone know if this will ever be implemented in spacewalk, or if it's been turned down in the past? On Wed, Aug 15, 2018 at 3:17 PM Bill Howe wrote: > We use cron to run a

Re: [Spacewalk-list] server says client should be updated, but nothing happens

We use cron to run a "date checker" type script. The date checker script can add the functionality you describe (first Monday). The script will determine whether or not to execute a python scheduler script. (this uses the python API to schedule updates) The example below executes a date checker

Re: [Spacewalk-list] server says client should be updated, but nothing happens

So there's no easy way to schedule all machines to update, say once a month on the first Monday, or something like that? How do you folks generally schedule and kick off your updates? On Mon, Aug 13, 2018 at 5:25 PM David Rock wrote: > > > On Aug 13, 2018, at 16:09, Guy Matz wrote: > > > >

Re: [Spacewalk-list] server says client should be updated, but nothing happens

> On Aug 13, 2018, at 16:09, Guy Matz wrote: > > Hi! In the Spacewalk UI I see: > Software Updates AvailablePackages: 6 > > rhnsd is running on the client but the client does not get updated. Running > 'yum update' on the client would get it to update, but I think rhnsd is > supposed

[Spacewalk-list] server says client should be updated, but nothing happens

Hi! In the Spacewalk UI I see: Software Updates Available*Packages: * 6 rhnsd is running on the client but the client does not get updated. Running 'yum update' on the client would get it to