hi keith,
I have confirmed this will break osad on the client. The only way to get the
client to work after this is to stop osad, delete the osad-auth.conf file and
restart osad.
i don't believe this is necessarily the expected behaviour, and wasn't the
case with our installation before upgrading to 1.2, at which point we
found it was necessary to remove the osad-auth.conf on the clients, after
removing the jabberd database, in order for them to be able to successfully
connect to to the server again.
Is there a way to manage sm.db or not.
not entirely sure what you mean by this. but in our case, i have found
using sqlite to be more reliable. the relevant section from the sm.xml is:
<!-- Storage database configuration -->
<storage>
<!-- Dynamic storage modules path -->
<path>/usr/lib/jabberd</path>
<!-- By default, we use the MySQL driver for all storage -->
<!-- <driver>db</driver> -->
<driver>sqlite</driver>
if that is of any use.
there are some useful notes on osad in this bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=662593
which are worth reading through.
i haven't really had time to delve into all of this in great detail, and
have only really done enough to get things working on our installation, so
i'm no authority on the matter, but hope this is of some use.
many thanks,
richard
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
