[Spacewalk-list] pushing to client, not

m.roth2006 at rcn.com m.roth2006 at rcn.com
Fri Mar 27 20:13:06 UTC 2009


Jan,

>Date: Fri, 27 Mar 2009 21:06:21 +0100
>From: Jan Pazdziora <jpazdziora at redhat.com>  
>On Fri, Mar 27, 2009 at 02:16:43PM -0400, m.roth2006 at rcn.com wrote:
>>
>> Wish it did. For some reason, osad wasn't running. I started it as a service, and scheduled a push of just one package. Went right away...
>
>So, pushing to clients obviously helps.
>
>> and failed, with exactly the same error I had before in /var/log/up2date, that yum couldn't find repomd.xml
>> 
>> So, is there anyone out there who can tell me if I need to generate, in spacewalk 0.4, the repomd.xml's for each channel?
>> 
>
>No, you don't. The repomd.xml gets generated on the fly by Spacewalk
>server (unless you've messed with its configuration and prevented
>it from doing so).
<snip>
Ok, so what configuration file would have an option that would prevent spacewalk? What do I need to do to enable that functionality? I've read as many man pages as I can find that might tell me, and I haven't seen anything about that.

       mark




More information about the Spacewalk-list mailing list