lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No countdown today


From: Thomas Morley
Subject: Re: No countdown today
Date: Sat, 14 May 2016 14:26:58 +0200

2016-05-14 11:52 GMT+02:00 Trevor Daniels <address@hidden>:
>
> David Kastrup wrote Saturday, May 14, 2016 9:19 AM
>
>> James <address@hidden> writes:
>>
>>> It seems that there is some intermittent issue at Savannah.gnu.org
>>> that is stopping me from pulling or fetching (I am getting either
>>> 'SSH-message' errors or 'fatal read' errors.
>>>
>> I got it mostly under control by reducing my MTU to 1400 from its
>> default of 1500 on my wireless interface.  It would appear that
>> something was not dealing gracefully with packet fragmentation and/or
>> size.  While I consider it most likely to have been a problem at my end,
>> it is at least conceivable that it might be a problem with the FSF's
>> network connections.  Though I think that Savannah is on quite a
>> different net than most of the gnu.org stuff, so that's a bit unlikely.
>>
>> At any rate, just wanted to throw this out for people who might want to
>> try whether fiddling with the MTU might make any difference with their
>> setup.
>
> I had a similar problem 6 years ago which was resolved by
> changing the MTU value.  The details are recorded here:
>
> http://lists.gnu.org/archive/html/lilypond-devel/2010-02/msg00400.html
>
> Just in case these problems are something similar ...
>
> Trevor
>



Can't get anything here to work.
Tackling MTU doesn't help either.

https://savannah.gnu.org/
states under Latest News:

Savannah suffering networking problems
     posted by rwp, Fri 13 May 2016 10:58:25 PM UTC - 0 repliesLast
Friday May 6th Savannah was moved to new hosting in the same
datacenter with many various assorted related and unrelated changes.
Since that time there have been wide spread reports of networking
problems. The FSF admins are aware of the problem and are trying to
resolve it.

Hope they've success soon,
  Harm



reply via email to

[Prev in Thread] Current Thread [Next in Thread]