James Bowes wrote:
Hi gang:
Attached is a patch to fix some of the slightly broken logic presenting
available z-stream/eus channels during registration. Please see the
commit message on the attached patch for a detailed explaination.
AFAIK this removes the only read of the is_default column in
James Bowes wrote:
Hi gang:
Attached is a patch to fix some of the slightly broken logic presenting
available z-stream/eus channels during registration. Please see the
commit message on the attached patch for a detailed explaination.
AFAIK this removes the only read of the is_default column in
Hi gang:
Attached is a patch to fix some of the slightly broken logic presenting
available z-stream/eus channels during registration. Please see the
commit message on the attached patch for a detailed explaination.
AFAIK this removes the only read of the is_default column in
rhnreleasechannelmap,
On Wed, May 27, 2009 at 09:46:26AM +0200, Jan Pazdziora wrote:
>
> Anyway, I'm going to add that Require to spacewalk-setup which will
> need spacewalk-cfg-get from spacewalk-backend, but maybe we want to do
Oops, in the end it looks the spacewalk-cfg-get will be used from
spacewalk-selinux (wher
Hello,
is it OK that no packages besides spacewalk-selinux Requires
spacewalk-backend?
If I do
rpm -e --nodeps spacewalk-selinux
on my installation,
rpm -e spacewalk-backend
then runs just fine. Shouldn't rnearly all spacewalk-backend-*
packages Require spacewalk-backend?
An
Jan Pazdziora wrote:
Hello,
I'm about to add script
/usr/bin/spacewalk-cfg-get
to spacewalk-backend-tools. The script can be used to reliably retrieve
configuration values from /etc/rhn/rhn.conf from non-Python
environments, without having to do grep or awk, which have potential
issues
On Tue, May 26, 2009 at 03:04:11PM -0300, Devan Goodwin wrote:
>
> > Also, Mirek said he would like to use such a thing in Proxy but
> > proxy only uses spacewalk-backend, not spacewalk-backend-tools.
> > Would you object having such a /usr/bin script in spacewalk-backend?
> > Presently the packag
Jan Pazdziora wrote:
On the other hand, having the scout run on the same Spacewalk server
is just one possible setup. It can also run on Proxies and it will
probably be hard to shut down the scout on Proxies as well. Are we
OK with the scout on Spacewalk server behaving differently from the
Proxy
Mike McCune wrote:
I would expect it to disable both the Monitoring and the MonitoringScout
service. Leaving the scout running while the Monitoring service is
disabled is largely pointless and confusing.
In fact it can be usefull. If you shutdown Monitoring and not Monitoring
Scout, then Scou
