anks,
Brett
On Mon, 10 Jan 2005 13:40:23 +0100, Corinna Vinschen
<[EMAIL PROTECTED]> wrote:
> On Jan 10 22:09, Brett Porter wrote:
> > Hi,
> >
> > I'm having a problem with my SSH client hanging executing a remote
> > command extracting an uncompressed tar. This o
Hi,
I'm having a problem with my SSH client hanging executing a remote
command extracting an uncompressed tar. This occurs on different
servers (FreeBSD, localhost Cygwin SSHD, RHL9), though they are all
SSH2 and I've using the same private DSA key.
Given this, it isn't the tar executable (though
Is there any reason this isn't part of the cygwin
distro.? I would have thought they went along with
libc, etc.
I can think of a couple of reasons: size, extra
maintenance time. Both fair enough. But I wonder if it
isn't a hassle if it might be a good idea. I remember
back to my DJGPP days where
> No. The new path setting is only good for *called*
> processes in the
> same fork/exec chain. The parent shell's PATH is
> not modified, so once
> 'autoconf' finishes and you drop back into your
> interactive shell, your
> old PATH is back in effect.
>
Sorry, I must have misunderstood. The
I have a couple of questions regarding this (apologies
if already covered - I'm on the digest and only got
this message on announce).
Let's see if I understand correctly:
1. you run autoconf
2. it sets the path based on a wrapper script
3. next execution goes to the desired one directly.
Doesn't
5 matches
Mail list logo
