From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1245 invoked from network); 4 Aug 2003 16:31:06 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 4 Aug 2003 16:31:06 -0000 Received: (qmail 23314 invoked by alias); 4 Aug 2003 16:30:55 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6445 Received: (qmail 23304 invoked from network); 4 Aug 2003 16:30:55 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 4 Aug 2003 16:30:55 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [4.64.233.107] by sunsite.dk (MessageWall 1.0.8) with SMTP; 4 Aug 2003 16:30:54 -0000 Received: (from schaefer@localhost) by candle.brasslantern.com (8.11.6/8.11.6) id h74GUr416322 for zsh-users@sunsite.dk; Mon, 4 Aug 2003 09:30:53 -0700 From: Bart Schaefer Message-Id: <1030804163053.ZM16321@candle.brasslantern.com> Date: Mon, 4 Aug 2003 16:30:53 +0000 In-Reply-To: <20030804111148.GA5224@spiegl.de> Comments: In reply to Andy Spiegl "interactive shell with ssh" (Aug 4, 1:11pm) References: <20030804111148.GA5224@spiegl.de> X-Mailer: Z-Mail (5.0.0 30July97) To: ZSH User List Subject: Re: interactive shell with ssh MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Aug 4, 1:11pm, Andy Spiegl wrote: } } Is there any way to execute commands on remote hosts allowing user } interaction and everything - just as if I would first login with an } interactive shell and then execute these commands??? To expand somewhat on Dan Nelson's answer: You can execute _one_ command on a remote host that way with ssh -e none -t remoteuser@remote.host "remotecommand ..." If what you have is a whole series of commands to automate "as if" you had typed them, you have the problem of needing to know exactly when a user interaction will occur -- there aren't separate input streams for commands vs. user input. The closest you might get is to assemble a shell script file of the commands to be executed, "scp" that to the remote host, then "ssh -t" to the same host to run the script as the single remote command. But that introduces the need to be security conscious that the file you execute is really the same one you scp'd.