From owner-freebsd-current Tue Mar 7 20:10:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 1982937B6DD for ; Tue, 7 Mar 2000 20:10:30 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115221>; Wed, 8 Mar 2000 15:11:20 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: ssh strangeness in -current... In-reply-to: <200003080253.DAA97113@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Wed, Mar 08, 2000 at 01:55:45PM +1100 To: freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.151120est.115221@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <8a447c$cfc$1@atlantis.rz.tu-clausthal.de> <200003080253.DAA97113@dorifer.heim3.tu-clausthal.de> Date: Wed, 8 Mar 2000 15:11:20 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-08 13:55:45 +1100, Oliver Fromme wrote: > I also had to remove >/etc/ssh. Somehow, /usr/local/bin/scp seems to pick up data >from /etc/ssh and tries to invoke /usr/bin/ssh, no matter >what. :-( I can't explain that. My installed-from-ports scp exec's /usr/local/bin/ssh1 and that ssh doesn't know anything about /etc/ssh. Try running "ktrace -i" on the scp and looking at what is actually exec'd and opened. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message