sftp client

[Corinna Vinschen]

On Wed, Feb 07, 2001 at 09:43:53AM +1100, Damien Miller wrote:
> On Tue, 6 Feb 2001, Corinna Vinschen wrote:
> > Just hit another problem. When connecting with openssh-sftp to
> > the sftp-server the sftp-server process remains in memory after
> > exiting the client, waiting for input.
> > 
> > sftp-server on i686-pc-cygwin,
> > sftp-client on i686-pc-cygwin and i686-pc-linux-gnu
> > 
> > The same does not happen when using the ssh.com sftp client.
>  
> Does the parent sshd exit?

Yes.

> Can you turn on debugging in the sftp-server by editing the #define TRACE 
> to use log instead of debug. I would like to see whether ssh.com sftp 
> sends an explicit close message.

Session:

	$ sftp cvaio
	sftp> pwd
	/home/corinna
	sftp> ^D

Log with ssh.com sftp:

sftp-server :  Cygwin Process Id = 0x63C : client version 2  
sftp-server :  Cygwin Process Id = 0x63C : realpath id 0 path . 
sftp-server :  Cygwin Process Id = 0x63C : sent names id 0 count 1 

Log with openssh sftp:

sftp-server :  Cygwin Process Id = 0x5D4 : client version 2  
sftp-server :  Cygwin Process Id = 0x5D4 : realpath id -1560921021 path . 
sftp-server :  Cygwin Process Id = 0x5D4 : sent names id -1560921021 count 1 

Is that helpful?!?

Corinna

BTW: What's about the patch to sftp-client.c I sent two days ago which
solves the "Couldn't close file: No Such File" problem?

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen at redhat.com