Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2003:
[Freeciv-Dev] Re: (PR#977) Extended connect dialog
Home

[Freeciv-Dev] Re: (PR#977) Extended connect dialog

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
Cc: vasc@xxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: (PR#977) Extended connect dialog
From: "Daniel L Speyer" <dspeyer@xxxxxxxxxxx>
Date: Thu, 28 Aug 2003 06:16:21 -0700
Reply-to: rt@xxxxxxxxxxxxxx

design-board@xxxxxxxxxxx wrote:

>On Thu, Aug 28, 2003 at 05:37:38AM -0700, Daniel L Speyer wrote:
>  
>
>>Christian Knoke wrote:
>>
>>    
>>
>>>There is still the - more general - problem with crashes: stale civservers,
>>>no logs if the server crashes.
>>> 
>>>
>>>      
>>>
>>True, only a server-side solution can address that (-quitidle or 
>>similar).  I considered that, but I found that if the client crashed, it 
>>was nice to be able to reconnect to the server and pick up my game.  
>>Admittedly, this is helpful for those who know how to do that, and 
>>clutters those who don't, but ti doesn't happen often, and stale 
>>civservers aren't dangerous.
>>    
>>
>
>Ok, but when CVS is concerned, this will happen rather often. So there
>should be a way to give the civserver the --log option.
>  
>
It already sends its stdour/err to .civserverlog<port#> at debug level 
3.  Does --log get even more information?  If so, then we may as well 
use it (though it would be nice for everything to go to one place.

--Daniel

>Christian
>
>  
>





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