Re: [Thinstation-general] Odd ssh problem

[Shotton J. <Jol...@hf...>]

>It=20looks=20like=20either=20thinstation=20adds=20an=20unneeded=20/=20
>to=20the=20start=20of=20HDUPDATE_PATH=20or=20COPSSH=20for=20Win32=20
>doesn't=20handle=20it=20correctly.

>Either=20way=20I=20think=20anyone=20using=20this=20combination=20
>will=20have=20better=20results=20removing=20the=20forward=20slash=20
>from=20the=20front=20of=20whatever=20gets=20passed=20as=20HDUPDATE_PATH.

Or=20indeed=20by=20making=20a=20symbolic=20link=20called=20'ts'=20from=20t=
he=20true=20copssh
root=20to=20the=20ts=20subdirectory=20of=20the=20effective=20root=20of=20t=
he=20ssh=20connection
-=20much=20easier=20and=20doing=20the=20job=20for=20me.

I=20would=20be=20interested=20to=20know=20where,=20if=20anywhere,=20the=20=
fault=20lies=20-
should=20copssh=20behave=20in=20this=20way?

Does=20thinstation=20hdupdate=20using=20scp=20work=20perfectly=20well=20on=
=20all=20linux
implementations=20of=20ssh?


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=20=20=20=20This=20email=20has=20been=20scanned=20for=20Virus=20infection=20=
by=20MessageLabs
=20=20=20=20=20For=20more=20information=20please=20contact=20messagelabs@a=
tomwide.com=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D