|
From: | Cory Coager |
Subject: | Re: [Duplicity-talk] hostname mismatch? |
Date: | Wed, 20 Mar 2013 18:40:41 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 |
Here is an example, address@hidden:~# hostname -f bane.underworld.site address@hidden:~# grep Hostname /var/tmp/duplicity/archive/*/*.manifest/var/tmp/duplicity/archive/37f4b2c022e95cd1688d9494301250e4/duplicity-full.20130307T020107Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-full.20130307T020107Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130307T020107Z.to.20130308T000006Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130308T000006Z.to.20130312T000002Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130312T000002Z.to.20130313T000003Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130313T000003Z.to.20130315T000003Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130315T000003Z.to.20130318T000001Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130318T000001Z.to.20130319T015518Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130319T015518Z.to.20130320T015247Z.manifest:Hostname bane /var/tmp/duplicity/archive/f0aa793a512357828638553ab075ef1d/duplicity-inc.20130320T015247Z.to.20130320T024531Z.manifest:Hostname bane
hostname returns the fqdn but duplicity is using the shortname. On 03/20/2013 07:30 AM, Kenneth Loafman wrote:
Duplicity obtains the hostname from the Python call socket.getfqdn(), so if the host names are set up the same way on each machine, it should return the fqdn if you've supplied it, or the simple hostname if not. A simple way to check is 'hostname -f' from the command line. I've found that the Python call returns the same answer. ...Ken On Wed, Mar 20, 2013 at 4:59 AM, <address@hidden> wrote:On 20.03.2013 04:36, Cory Coager wrote:Regarding the duplicity manifest file for hostname, why does duplicity use the short name sometimes and the fqdn other times? There doesn't seem to be any consistency. I have 12 servers created from the same template, 8 are using the short name and 4 are using the fqdn. Any idea why? I'm noticing this is an issue recently because one of my servers started complaining about, "Fatal Error: Backup source host has changed." I'd rather avoid --allow-source-mismatch if I can. How can I make this consistent with fqdn's?to my knowledge only the source path is saved and compared resulting in the error above. unfortunately i never had a look at that part of the source. Ken: any idea? ..ede_______________________________________________ Duplicity-talk mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/duplicity-talk
[Prev in Thread] | Current Thread | [Next in Thread] |