Anthony Messina wrote:
There is a bug in setup-ds-admin.pl -u - it does not delete the old fedora ds instances when upgrading to 389. You can ignore those old instances.On Saturday 15 August 2009 04:42:52 pm Anthony Messina wrote:On Saturday 15 August 2009 04:31:51 pm Anthony Messina wrote:See /usr/share/dirsrv/html/java/ contains and what version of console is used.sorry, i forgot the versions... 389-admin-1.1.8-3.fc11.x86_64 389-admin-console-1.1.4-1.fc11.noarch 389-admin-console-doc-1.1.4-1.fc11.noarch 389-adminutil-1.1.8-3.fc11.x86_64 389-console-1.1.3-3.fc11.noarch 389-ds-1.1.3-4.fc11.noarch 389-ds-base-1.2.1-1.fc11.x86_64 389-ds-console-1.2.0-4.fc11.noarch 389-ds-console-doc-1.2.0-4.fc11.noarch 389-dsgw-1.1.4-1.fc11.x86_64 idm-console-framework-1.1.3-1.fc11.noarchI have reinstalled 389 DS on my master and slaver servers, from scratch and do not experience any issues. Unfortunately, I'm not so sure about what setup- ds-admin.pl -u should be doing, as it did not properly update eithe rof my machines and it left the old instances of fedor-ds in the console.
------------------------------------------------------------------------ -- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
<<attachment: smime.p7s>>
-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users