Do to firewall issues, sometimes it is impossible to run a local copy of 389-console that can connect on all the correct ports. On the other hand, I'msure we have all experienced how slow 389-console is over ssh. To work around this, I install xpra on my server and remote client. Now I can do a: ssh server.server "xpra start :1001 --start-child 389-console" && \ xpra attach ssh:server.server:1001 && \ ssh server.server "xpra stop :1001" This first starts 389-console on the server with X going to a headless X server. Then the local machine connects to that server. Finally when done, the server at the distant end is closed. This is optional. You could leave it running all the time. Benefit is really fast 389-console with only firewall holes for ssh port. xpra is at: http://xpra.org and their is a fedora package review at: https://bugzilla.redhat.com/show_bug.cgi?id=651591 Joel -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
