Re: [Duplicity-talk] ioctl sign extension on FreeBSD 6.3 amd64

[Philip Jocks]

Ken,

I removed the pexpect.py* files and symlinked them from the files the FreeBSD 
port installed (/usr/local/lib/python2.6/site-packages/pexpect.py*).
Seems to work, at least, there wasn't any error thrown when I ran an 
incremental backup and a collection-status.
Anything else that might need testing to be sure?

Philip

Am 15.09.2010 um 15:38 schrieb Kenneth Loafman:

> We ship pexpect.py with duplicity as a convenience and with the author's 
> blessings.
> 
> It could be replaced with the current version if you want to try it...  let 
> us know.
> 
> ...Ken
> 
> Philip Jocks wrote:
>> Hi Ken,
>> 
>> sorry for digging this out, but I just ran into this issue again, with 
>> duplicity installed from FreeBSD ports on a 8.1 amd64 box.
>> I asked someone I know who is more familiar with Python than I am and we 
>> found out that the pexpect.py you ship with duplicity causes this in line 
>> 1448:
>> 
>>   
>> 
>>>         fcntl.ioctl(self.fileno(), TIOCSWINSZ, s)
>>>     
>>> 
>> 
>> Uncommenting it lets the warning disappear and duplicity seems to continue 
>> to run OK. If I understood the Python guy correctly, it doesn't really 
>> matter, because this is about setting the terminal window size and sftp/scp 
>> et al don't really care about that.
>> 
>> Maybe, someone can confirm and fix this somehow. If I'm not mistaken, 
>> rsync.net was/is sponsoring duplicity and they're a FreeBSD shop, so it 
>> should be easy for them to reproduce and confirm.
>> 
>> Is that pexpect.py a specially tuned version of the module and necessary to 
>> keep and not just depend on the current one?
>> 
>> Philip
>> 
>> Am 09.03.2009 um 22:55 schrieb Kenneth Loafman:
>> 
>>   
>> 
>>> I have never tested on FreeBSD.  If someone in the group knows what's
>>> going on here, please let us know.  Haven't looked at BSD in years!
>>> 
>>> ...Ken
>>> 
>>> Philip Jocks wrote:
>>>     
>>> 
>>>> Same problem here on FreeBSD 7.1 p2 amd64. First backup seems to work,
>>>> further backups die with
>>>> -- 
>>>> Fatal Error: Neither remote nor local manifest is readable.
>>>> No old backup sets found, nothing deleted.
>>>> -- 
>>>> Does anyone has an idea how to fix this?
>>>> 
>>>> Cheers,
>>>> 
>>>> Philip
>>>> 
>>>>       
>>>> 
>>>>> Separate from my cron issues, I see the following in my kernel log
>>>>> when duplicity runs:
>>>>> 
>>>>> WARNING pid 72869 (python2.5): ioctl sign-extension ioctl
>>>>> ffffffff80087467
>>>>> 
>>>>> This is on FreeBSD 6.3 amd64, current Python, etc. installed from ports.
>>>>> 
>>>>> It seems to show up once each time it connects to the remote host,
>>>>> with a different pid each time.  I know the warning is actually coming
>>>>> from Python, but the first time I Googled for this (admittedly, a
>>>>> while ago; can't find links now), some other projects had similar
>>>>> issues and the fix was in the project itself, not Python.
>>>>> 
>>>>> -- 
>>>>> Steve Madsen 
>>>>> <address@hidden>
>>>>> 
>>>>> Light Year Software, LLC  
>>>>> http://lightyearsoftware.com
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> 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
>>>> 
>>>> 
>>>>       
>>>> 
>>> _______________________________________________
>>> 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
>> 
>> 
>>   
>> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk