All,
I am running Spacewalk 2.8 on Centos 7.x. I have noticed /var/run/yum.pid
files being created early morning (around 5.30am) on Centos *6* servers ONLY.
I thought it might be the yum-cron service running yum - but it is disabled. I
also see in Spacewalk that the time of last checkin
the
coming week. Once the next audit rolled around we could just pull out
these plans and prove that we had kept up with security patching.
Let me know if you have further questions.
Kind regards,
Steve
Am 2019-01-22 19:45, schrieb Dave Thoms:
> I have a Spacewalk 2.8 install on CentOS 7.x
I have a Spacewalk 2.8 install on CentOS 7.x. I've done a fair amount of
digging to understand what errata actually is. Why it's needed when you are
already getting all updates. Whether it applies to ALL repos or just the
official ones for CentOS. Does anyone have a handle on this -
for CentOS 6 is http://mirror.centos.org/centos/6/updates/x86_64/.
From:
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
mailto:spacewalk-list-boun...@redhat.com>>
On Behalf Of Dave Thoms
Sent: Thursday, January 17, 2019 5:06 PM
To: spacewalk-list@redhat.com&
ri
From: spacewalk-list-boun...@redhat.com On
Behalf Of Dave Thoms
Sent: Thursday, January 17, 2019 4:41 PM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] Repo question...
I am using Spacewalk 2.8 on CentOS 7. I still have lingering CentOS 6
(technically 6.10) machines that need updates.
I am using Spacewalk 2.8 on CentOS 7. I still have lingering CentOS 6
(technically 6.10) machines that need updates. I noticed that the amount of
update that updates available for my 6.10 machines under a local yum update are
different that what Spacewalk offers. So I did some digging via
/%40spacewalkproject/spacewalk-2.8-client/epel-7-x86_64/
since x64 is the only arch available for EPEL (as opposed to on fedora where
x86 is still built also, but I also specify x64 there since I don't have any
x86 fedora clients).
Bruce Wainer
On Tue, Aug 14, 2018 at 12:25 AM, Dave Thoms
I should have said I REPLACED the line in the spacewalk.repo.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Dave Thoms
Sent: Monday, August 13, 2018 9:54 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk - remote command option -
rhncfg-actions RPM not found
I
/@spacewalkproject/spacewalk-2.8-client/epel-7-$basearch/
The client repo is the one you need for rhncfg-actions.
On Mon, Aug 13, 2018, 12:24 PM Dave Thoms
mailto:dav...@truhearing.com>> wrote:
Sorry about the missing carriage returns:
(the double spacing is not in the original file)
[root
/rpm-gpg/RPM-GPG-KEY-spacewalk-2.8
enabled=1
gpgcheck=1
[root@dev_1 yum.repos.d]#
-Original Message-
From: spacewalk-list-boun...@redhat.com On
Behalf Of Dave Thoms
Sent: Monday, August 13, 2018 11:17 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk - remote
My repo file:
[root@dev_1 yum.repos.d]# cat spacewalk.repo
[spacewalk]
name=Spacewalk
baseurl=https://copr-be.cloud.fedoraproject.org/results/@spacewalkproject/spacewalk-2.8/epel-7-$basearch/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-spacewalk-2.8
enabled=1
gpgcheck=1
[root@dev_1 yum.repos.d]#
have them
enabled?
If not, follow step one, depending on your os of this HowTo:
https://github.com/spacewalkproject/spacewalk/wiki/RegisteringClients
Tomáš
On Thu, Aug 9, 2018 at 11:57 PM, Dave Thoms
mailto:dav...@truhearing.com>> wrote:
All,
I recently just installed Spacewalk 2.8 in Cento
All,
I recently just installed Spacewalk 2.8 in Centos 7. In the web GUI if you go
to Systems and then Remote Command I get the message:
Remote Command on dev.local.com
You must enable Remote Command execution on the target system by installing the
rhncfg-actions RPM.
I have looked high and
13 matches
Mail list logo
