I'm setting up a diskless, thin client computing cluster using LTSP local apps and LAM/MPI. LAM wants password-free ssh access, so I set up the authorization keys and can do remote commands using ssh without difficulty. The problem comes when some of the LAM tools and/or local apps want to write to /tmp. In the current configuration (I'm using K12LTSP 4.2.1) /tmp is read-only for the user. If I chmod it to read-write for the user in rc.sysinit, ssh is unhappy and won't connect.
In the early days of LTSP, I did this via rsh, .rhosts, etc, but these days this is discouraged in favor of ssh for security reasons. Is it possible to configure ssh to ignore or accept user read-write permissions on /tmp? ------- John L Bartelt [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
