patches for UnixWare v2.x pty (misc.c,configure.in)

[Tim Rice]

On Mon, 12 Feb 2001, Tom Rudnick wrote:

> > > The second patch adds a section "*-*-sysv4.2uw2*" to configure to
> > > set the TEST_MINUS_S_SH shell and define USE_PIPES.
> > 
[snip]
> > What are you seeing that USE_PIPES fixes?
> > Ie. How can I duplicate the problem here.

It looks like USE_PIPES is needed.
Now that I think of it, all my scp usage has been from UnixWare to 
some other non UnixWare platform.
I can duplicate the problem on UnixWare 2.03, UnixWare 2.13,
and UnixWare 7.1.0 (*-*-sysv5*)

I do not think "*-*-sysv4.2uw2*" is needed.
I would be suprised if other sysv4.2 did not also have this problem.

> > 
> I brought forward USE_PIPES from scp hanging problems in 2.3.0p1.
> They still exist in the version I just built from today's cvs.
> 
> After completing a copy, the client returns a prompt, but the
> session is still active (still has  "sh -c scp -t file", 
> "scp -t file", and "sshd" active on the server, plus ssh command 
> on client).
> 
> Typing an INTR on the client returns an error of "Killed by signal 2",
> at which point everything exits.
> 
> To test it, I ran:
> 
> scp file localhost:file.2
> 
> I also tested scp from a remote 2.3.0p1 client with the same results.
> 
> Let me know if you can duplicate this or not.
> 
> -Tom
> 
> 

-- 
Tim Rice				Multitalents	(707) 887-1469
tim at multitalents.net