On Tue, 4 Mar 2003 [EMAIL PROTECTED] wrote: >Background X whenever you start it up >ssh $machine "/usr/bin/X11/X &"
In general, I find it more elegant to use the -f option to fork off the ssh connection, but in this case, it might be better to change that up a little and do 'ssh $machine "/usr/bin/X11/X" &' after which you can grab the PID from $! for later killing. Your #2 problem should be unrelated and just sounds all kinds of wrong unless you're intentionally running some kind of low-security environment like a QNX realtime system or something. How are you invoking X? I presume you need to launch some sort of client and not just the X server. Are you using xinit? startx with a .xsession file? Unless you are subsequently pushing the display of a client from the controlling machine to the distributed machines, in which yucky case it wouldn't be unexpected that you had to disable X security to make that work, but I hope you're not doing that. >> 1. When using the startX on all machines script, >> it doesn't run quietly in the background, you have >> to ctrl-C to move on to the next machine. The >> output you see before you ctrl-C is: >> >> So this actually works, since X is launched >> succesfully on each machine. >> >> It would be nice for this not to happen. I don't >> know enough about X to figure out a different way >> of launching it without having to do the ctrl-C >> thing. >> >> 2. X access control is disabled. If anyone ssh's >> into the machine, they can run X programs. It >> would be nice to change this. >> >> 3. The kill X script has to be run as root, since >> X runs as root. It would be nice to have some way >> to kill X without doing it as root. >> Eric Irrgang _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://www.utacm.org/mailman/listinfo/siglinux
