[Tilesathome] Client Stability

[Jason Reid]

The other option is to 'chattr +i ~/.inkscape/preferences.xml' which 
makes the file immutable, and as such it can't become corrupted. Biggest 
problem here is that chattr has to be run from root under most systems, 
though I wouldn't think this would be too large an obstacle until a 
better solution is implemented.

-Jason Reid

Milenko wrote:
> True, I didn't consider the fact that inkscape isn't just used for the t at h 
> client.  Can the inkscape preferences file be specified in the command-line? 
> That way a custom t at h preferences files could be used in the t at h directory 
> and that file could be deleted every loop.  Or your method could also work, 
> I'm not 100% sure what it does.  :)
>
> -Jeremy
>
> ----- Original Message ----- 
> From: <matthew-osm at newtoncomputing.co.uk>
> To: "Milenko" <milenko at king-nerd.com>
> Cc: <tilesathome at openstreetmap.org>
> Sent: Friday, December 07, 2007 8:37 AM
> Subject: Re: [Tilesathome] Client Stability
>
>
>   
>> Hi,
>>
>> On Fri, Dec 07, 2007 at 08:21:51AM -0500, Milenko wrote:
>>     
>>> I've run across two issues that seem to keep recurring, both of which 
>>> will
>>> cause the client to die and be manually restarted.  First one is the 
>>> inkscape
>>> preferences file, which seems to get b0rked any time inkscape crashes. 
>>> Since
>>> the fix is to delete the /home/user/.inkscape directory and restart the
>>> client, couldn't the client simply do this at the start of every loop? 
>>> That
>>> way inkscape will generate a new preferences file every loop and should 
>>> keep
>>> this from happening.  Unless this file is meaningful in some other way?
>>>       
>> Well, I wouldn't want my Inkscape preferences deleted by an automatic 
>> process
>> when I didn't know it was going to happen...
>>
>> However, a better way may be to set "HOME=`pwd`"[1] at the start of 
>> processing,
>> so you keep separate inkscape preferences for the t at h stuff. (Or 
>> equivalent on
>> Windows.)
>>
>> Incidentally, it also needs to unset the DISPLAY variable as this causes
>> problems with Inkscape if set. Recent Inkscape has a "don't use X" option
>> ("-z"), but older versions may not.
>>
>> Thanks,
>>
>> -- 
>> Matthew
>>
>> [1] Actually, something like "export HOME=$(dirname `readlink -f 
>> $TAH_PROG`)"
>> would be safer, in case not run from the tilesAtHome directory.
>>
>>     
>
>
>
> _______________________________________________
> Tilesathome mailing list
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome
>