I'm going to ask them to exempt this one. The spacewalk server is very
useful for managing large numbers of machines, and it sounds like this
would break some of that management capability.
On Thu, Jun 13, 2019 at 2:18 PM William Hongach
wrote:
> Hello,
>
>
>
> It is the service (or related
It would be of interest for me, why this should be shut down? It shouldn't
listen for connections. So what security concerns are there?
sent from my mobile device
Originale Nachricht
Von: William Hongach
Gesendet: Thu Jun 13 20:15:47 GMT+02:00 2019
An:
Hello,
It is the service (or related timer) that runs rhn_check based on the interval
specified in /etc/sysconfig/rhn/rhnsd. This is how Spacewalk clients check in
with the server for queued tasks. There should be a man page available for
rhnsd.
If you shut it down, the client will not
What is the actual function of rhnsd? What is actually being lost if its
not running?
On Thu, Jun 13, 2019 at 1:02 PM William Hongach
wrote:
> Hello,
>
>
>
> I suppose you could run rhn_check out of cron if you did not want rhnsd to
> schedule it.
>
>
>
> *From:*
Hello,
I suppose you could run rhn_check out of cron if you did not want rhnsd to
schedule it.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Paul Greene
Sent: Thursday, June 13, 2019 12:31 PM
To: Spacewalk-list@redhat.com
Subject: [Spacewalk-list] Is the rhnsd service required to be
Our security group is telling me, based on a Nessus scan, that I need to
disable the rhnsd service.
Is the rhnsd service required to be able to communicate with a spacewalk
server?
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
