On Sat, Apr 22, 2000 at 09:19:50AM +0200, Poul-Henning Kamp wrote:
>
> I have seen this problem with rsync as well. I think I solved it
> by downstepping to an older rsync version.
Which version do you use ?
I ask because using the old version on Freefall here as server
for the session doesn't
On Sat, Apr 22, 2000 at 02:47:58AM -0700, Kris Kennaway wrote:
>
> If you have a checked out copy of the ports collection in your home
> directory you can point to it with the PORTSDIR variable and everything
> will work fine. Having said that, an update of the /usr/ports dir would be
> good.
Ye
On Sat, Apr 22, 2000 at 09:19:50AM +0200, Poul-Henning Kamp wrote:
>
> I have seen this problem with rsync as well. I think I solved it
> by downstepping to an older rsync version.
Thanks !
--
Andreas Klemm http://people.FreeBSD.ORG/~andreas
On Sat, 22 Apr 2000, Andreas Klemm wrote:
> am not sure if this is related to my -current kernel or last recent
> ssh changes but perhaps you have an idea.
No idea on this, but:
> BTW, could someone on freefall please update the ports collection.
> Nothing works, if I want to build a port with
I have seen this problem with rsync as well. I think I solved it
by downstepping to an older rsync version.
Poul-Henning
In message <[EMAIL PROTECTED]>, Andreas Klemm writes:
>
>--UlVJffcvxoiEqYs2
>Content-Type: text/plain; charset=us-ascii
>
>Hi,
>
>am not sure if this is related to my -curre
Hi,
am not sure if this is related to my -current kernel or last recent
ssh changes but perhaps you have an idea.
Since yesterday I'm not able, to upload some files using rsync over ssh.
Attached is a short tcpdump.
netstat shows it this way:
input (xl0) output
