> Hi, thanks for answers
> So if I configure postfix, this will be enough?
Yes, it will.
> Or anything else what I need to write to spacewalk configuration file?
> Best Regards,
> Elsever Sadigov
System Management Engineering, Red Hat
Do you have found a solution to your repo?
From my side I’ve moved all my repos to an old directory but spacewalk will be
Before creating a crontab job to removing of these files automatically, I
wanted to know if another solution exists.
You can disable a repo as described below – if done correctly then it shouldn’t
show up with “yum repolist enabled” any longer. If you mean stop syncing a
repository, though, that can be done from the WebUI as below:
Channels -> Manage Software Channels -> Click Channel Name -> Repositories ->
On 2019-02-22 22:30, Robert Paschedag wrote:
> On 2/22/19 7:53 PM, Robert Paschedag wrote: Am 22. Februar 2019 13:11:00 MEZ
> schrieb Florin Portase : On 2019-02-13 10:56,
> Florin Portase wrote:
> I just have upgraded the spacewalk server from 2.7 => 2.9.
> I have applied
Not sure if this is your case, but I did had this same issue by installing
the rhn packages from this Opensuse repository :
I did create this ticket :
Take a look at Steve's scripts and you can get the errata added to
Spacewalk for all the CentOS repos.
Excellent scripts, been using them to get errata into Spacewalk for years.
Wish CentOS would just provide the errata in the repos like red hat,
You could use activation keys that map to certain base/child channels.
Then just run a registration script on the system (shameless plug example:
You may also be able to use distribution channel mappings, but I haven't
The API has excellent documentation if you don't quite find what you are
On Mon, Feb 18, 2019, 09:41 Matthias Gruber wrote:
> Oh... thats sound good... I am back in that stuff tomorrow
> Thanks a lot
see the subject. Does someone use "unattended-upgrades" while getting the repos
Does it work?
In case it does work, what settings do you set within the config?
A customer showed me, that the "unattended-upgrades" does not work with the
"default" settings. Also it
We are trying to figure out how to automate registering our servers with
specific repositories. Currently, we kickstart new servers and have them
register to spacewalk using a universal activation key that has no channels
associated with it. We did this so that when we create new frozen
Mail list logo