On 1/14/09, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Wed, Jan 14, 2009 at 11:35:49AM +0000, travellig travellig wrote: >> >> >> >> osa-dispatcher is only needed if you wanna use osad from the clients. >> >> Since osad is not a default package, I don't see why osa-dispatcher >> >> should be installed by default with spacewalk. >> > >> > One reason is that if the client in fact installs osad and tries to >> > use Spacewalk, it won't work. >> >> This comes as a surprise since I got osad->osa-dispatcher<->jabberd >> working nicely in my environment (0.3). I remember though that it was >> not an straight forward configuration. > > Right. On the other hand, if you remove that osa-disparcher and > jabberd from the server, that osad won't work because it doesn't have > the server side to connect to.
I would expect that to be the case not just for osad but for any other client/server scenario ;) I think, I slightly misunderstood where you were coming from. > >> > Another reason for having at least jabberd installed in default >> > spacewalk installation is bugzilla 479971 -- we create jabberd >> > configuration, and if would be nice to create it only after the >> > package was in fact installed, otherwise the files are owned by root >> > and jabberd won't be able to use them. >> >> Any chance of sharing the bugzilla number that states this issue with >> osad/osa-dispathcer/jabberd? > > 479971. Thanks for that. -- travellig. _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
