On Sat, Jan 10, 2009 at 04:04:03PM -0600, Harry P wrote: > Osamu Aoki <os...@debian.org> writes: > > On Sat, Jan 10, 2009 at 09:26:07AM -0600, Harry P wrote: > >> Axel Freyn <axel-fr...@gmx.de> writes: > >> > Why do you use ssh to connect to the local machine? I would propose to > > Point of Axel is use of SSH wastes CPU resource while gaining nothing. > > His suggestion is more efficient. .. I think. > Setting the issue of whether you have to type out a passwd aside:
Hmmm... you must have set up passwordless SSH to root. I hope this sshd is not accessible from Internet. You may be attacked easily. You can set sudo not to request password to become root too. (Setting this up like this also makes your user's system less secure but at least intruders must have shell access first with sudo.) > I'm not so sure about the efficiency angle. It appears to take no > config whatever for ssh -X to just work. Plus, it appears to be > portable with no extra vars to set or files to edit. It just works > from one machine to another, and it blends right in with my usage > practice established over many yrs and fairly ingrained by now. I know you have fast machine and your machine's default for sshd happened to worked for you. But If sshd was not configured to be started or PermitRootLogin was not set for it, you were out of luck. So knowing one method is good but it will not harm to know the alternative method and its limitations. ... > All that said it is another way to get the results I wanted and > appears to be fairly easy to do... thanks to all of you. Cheers... Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org