Hi,
I was lookin for the diff file but couldn't find it.
Please, could you provide a link?
_
Reciba un cordial saludo
Roberto Navarro Reyes
Director Técnico - Tusprofesionales, SL
- Original Message -
From: Gerald Vogt v...@spamcop.net
To: spacewalk-list@redhat.com
Hi all,
Thanks for the suggestions, I'm trying to limit the need to invoke
anything from the deployed client. This is because:
1. It would save putting in security mechanisms to ensure only the
registered client make the call to Spacewalk
2. It would prevent issues where Spacewalk connectivity
Currently I have all necessary information for this connection:
[root@my_host ~]# egrep 'db_(host|name|port)' /etc/rhn/rhn.conf
db_name = swdb00
db_host = my_db_host
db_port = 5432
I will be testing the patch submitted earlier in this thread tomorrow
evening during a maintenance window for my
Hello all.
Now this maybe a little picky but I figure I would ask just in case there
might be a way. Since I myself probably won't be doing a lot of the spacewalk
client installs, I'm wondering if there is a way to force the OSA status to
show up after the client has been registered but
Hello all. Is there any way either a hack or a command line way to change the
data sent to the SW server upon registration? The system properties information
is basic and I would like to make it more realistic information. We run both
Oracle and RHEL and both show up an redhat-release-server
The OSA status should appear very shortly after osad is installed and the
service is started.
If this is not the case there may be issues with your OSA configuration.
On Sep 23, 2014 9:53 AM, Glen Collins glenc2...@comcast.net wrote:
Hello all.
Now this maybe a little picky but I figure I
