Once a profile is created I can't find a way to remove it.
--
Jim Kinney
Signature Technologies Lab
404-407-7967
smime.p7s
Description: S/MIME Cryptographic Signature
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mai
Running Spacewalk 1.2 and I have created several snippets for use in the post
section of the kickstart. I had to add the #raw/#endraw to the snippet to get
them to properly show up in the kickstart. Doing this seems to break the
ability to have a variable in the snippet.
I have a variable ETH=e
Hi,
I upgraded our Spacewalk installation to version 1.2 today and I'm now seeing
the error below in the rhn_taskomatic_daemon.log every 2 minutes. Does anyone
have any idea how to fix it?
I didn't see any errors during the upgrade process, although we are using an
Oracle 11g database so I've
* Is the service rhnsd running on the client?
* What happens when you run "rhn-check -v -v -v" on the client when
updates are scheduled?
On Thu, Feb 03, 2011 at 05:35:52PM +0200, Berezovski, Vladimir wrote:
> SW v. 1.2
>
> Having child updates channel for RH5.5 clients cannot update any
Check that there is a process listening on 5222. That is the jabberd port.
I haven't gotten any farther on this at the moment, but I did notice one thing;
in the documentation for the OSAD set up, it says to use the FQDN of the
spacewalk server. When we set this up, spacewalk detected the shor
Hi ,
The problem was in multiple Java version .
Installing the RHEL i386 as SW server and 32 bits java solve the issue .
Thanks .
Best regards ,
Vladimir Berezovski
NDS IL , Unix group
Email:
vberezov...@nds.com
-Original Message-
From: spacewalk-list-boun...@redhat.com
[m
Def. Quota Miroslav Suchý :
On 02/02/2011 10:47 PM, Benedetto Vassallo wrote:
I have some monitoring probes configured as "suite probes" and some
others configured ad "system probes".
When I select a system and then clicking in the monitoring tab I can
only see the suite probes but still con
On 02/02/2011 10:47 PM, Benedetto Vassallo wrote:
>
> I have some monitoring probes configured as "suite probes" and some
> others configured ad "system probes".
> When I select a system and then clicking in the monitoring tab I can
> only see the suite probes but still continuing to receive e-ma
