Date: Sat, 9 Sep 2000 02:44:46 -0700 From: michael@dynamine.net (Michael S. Fischer) To: cjclark@alum.mit.edu Cc: freebsd-questions@FreeBSD.ORG Subject: ANSWER: Re: ssh problem Message-ID: <20000909024445.B1504@dynamine.net> In-Reply-To: <20000907233258.J69158@149.211.6.64.reflexcom.com>; from cjclark@reflexnet.net on Thu, Sep 07, 2000 at 11:32:58PM -0700 References: <20000907141929.A3960@dynamine.net> <20000907233258.J69158@149.211.6.64.reflexcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 07, 2000 at 11:32:58PM -0700, Crist J . Clark wrote: > > While I can log in to my FreeBSD (-STABLE as of this AM) box via ssh > > (I'm using RSA authentication), I cannot run any commands on the ssh > > command line (e.g. 'ssh phoenix ls') and get a response. scp does not > > appear to work either to this particular host. > > Can you try running the client as, > > $ ssh -v <host> ls > > And the daemon on the server as, > > # sshd -d > > To get the debug output? I finally figured out what the problem was. After debugging my shell init scripts I found the following code which caused the session to hang in non-interactive mode: # Check for the presence of 'less'. bash returns 127 on `command not # found' errors. less >/dev/null 2>&1 if [ $? -eq 127 ]; then unset -v HAVE_LESS; else HAVE_LESS=yes; fi Changing this to # Check for the presence of 'less'. which less >/dev/null 2>&1 if [ $? -ne 0 ]; then unset -v HAVE_LESS; else HAVE_LESS=yes; fi Seems to have fixed the problem. -- Michael S. Fischer <michael@dynamine.net> AKA Otterley _O_ Lead Hacketeer, Dynamine Consulting, Silicon Valley, CA | Phone: +1 650 533 4684 | AIM: IsThisOtterley | ICQ: 4218323 | "From the bricks of shame is built the hope"--Alan Wilder net.goth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000909024445.B1504>