hooray! be that machine into submission!
Ter
On Feb 16, 2009, at 4:22 AM, Benjamin Niemann wrote:

> I think I found a way around the flaky firewall: corkscrew a tool that
> lets me make SSH connections over the HTTPS proxy. Now I could submit
> a CL through the tunnel over the proxy ;)
>
> -Ben
>
> On Mon, Feb 16, 2009 at 11:50 AM, Benjamin Niemann <[email protected]>  
> wrote:
>> Looks like the problem is indeed on my side. For some reason only
>> 'short' commands work, e.g. p4 edit or p4 sync (with not much to
>> sync). Initial sync of a new client also hangs. If I log into another
>> machine, it works there. And even if I make the connection through a
>> SSH tunnel, the tunnel connection will hang.
>>
>> -Ben
>>
>> On Sun, Feb 15, 2009 at 11:20 PM, Terence Parr <[email protected]>  
>> wrote:
>>> If you are on a mac and running the mail client, mail creates enough
>>> processes over three or four days that it kills the system you  
>>> have to
>>> restart mail every few days. astonishing right?
>>> Ter
>>> On Feb 15, 2009, at 1:52 PM, Benjamin Niemann wrote:
>>>
>>>> On Sun, Feb 15, 2009 at 7:54 PM, Terence Parr  
>>>> <[email protected]> wrote:
>>>>>
>>>>> weird.  try latest p4 command line client.  we updated p4d  
>>>>> daemon to
>>>>> latest.
>>>>
>>>> It already is, just reinstalled my system. But something seems to  
>>>> be
>>>> hosed with my system now, as even emacs refuses to start properly.
>>>> Perhaps the problem is on my side after all.
>>>>
>>>> -Ben
>>>>
>>>>
>>>>> Ter
>>>>> On Feb 15, 2009, at 7:46 AM, Benjamin Niemann wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> pink-macbookpro:~/projects/antlr3 ben$ p4 submit -c 5582
>>>>>> Submitting change 5582.
>>>>>> Locking 2 files ...
>>>>>> edit //depot/code/antlr/main/runtime/Python/antlr3/__init__.py#11
>>>>>> edit //depot/code/antlr/main/runtime/Python/setup.py#13
>>>>>> Perforce client error:
>>>>>>     TCP receive failed.
>>>>>>     read: socket: Operation timed out
>>>>>>
>>>>>> my first guess would be some limitation of the hotel wifi, but  
>>>>>> all
>>>>>> other p4 operations work and since P4 is constantly talking to  
>>>>>> the
>>>>>> server, I assume that it should either just work or not at all if
>>>>>> there's an issue on the network layer.
>>>>>>
>>>>>> Does any know some magic flag/env var that make p4 a bit more  
>>>>>> verbose
>>>>>> so I can see where it is hanging?
>>>>>>
>>>>>> -Ben
>>>>>> _______________________________________________
>>>>>> antlr-dev mailing list
>>>>>> [email protected]
>>>>>> http://www.antlr.org/mailman/listinfo/antlr-dev
>>>>>
>>>>>
>>>
>>>
>>

_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org/mailman/listinfo/antlr-dev

Reply via email to