Re: [Duplicity-talk] Hostname changes....

[edgar . soldin]

Rather try to find out how duplicity is determing the hostname and fix the root 
cause, enabling --allow-source-mismatch won't warn you anymore in case you 
really picked the wrong backup source.

ede/duply.net

On 02.01.2011 13:03, Chris Poole wrote:
> Try just using --allow-source-mismatch
> 
> Chris
> 
> On 1 Jan 2011, at 21:41, Scott Hannahs <address@hidden> wrote:
> 
>> I am getting an error every so often that tells me that my hostname has 
>> changed.  There seems to be a capitalization issue.
>>
>>
>> Fatal Error: Backup source host has changed.
>> Current hostname: diospyros.local
>> Previous hostname: Diospyros.local
>>
>> Now this seems to happen after I have connected and disconnected through VPN 
>> and the hostname has been reset?
>>
>> How is the hostname determined?  There are about 4 ways to get a "computer 
>> name" or "host name" on Mac OS X.  They are all giving me the capitalized 
>> name.  But duplicity is reporting that the current hostname is not 
>> capitalized.  It seems to be using either the "hostname" or "uname" 
>> functions.
>>
>> % hostname
>> Diospyros.local
>> % scutil --get ComputerName
>> Diospyros
>> % scutil --get LocalHostName
>> Diospyros
>> % uname -n
>> Diospyros.local
>>
>> As a proposal should duplicity be using a case independent comparison to see 
>> if the backup source host has changed?
>>
>> Mac OS X 10.6.5, duplicity version 0.6.11
>>
>> -Scott
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk