[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Duplicity-tracker] [bug #25138] Bad file descriptor on Cygwin
From: |
Poojan Wagh |
Subject: |
[Duplicity-tracker] [bug #25138] Bad file descriptor on Cygwin |
Date: |
Sun, 28 Dec 2008 03:54:15 +0000 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5 (.NET CLR 3.5.30729) |
Follow-up Comment #2, bug #25138 (project duplicity):
Hi, Ken. Based on your comments on a similar problem, I did try increasing
ulimit -n to 2048. I'm using duplicity 0.5.03. I also tried the
--short-filenames options as you suggested in that thread. Neither seem to
effect a solution.
Just in case, I tried setting the temporary directory elsewhere (a separate
drive, outside of the Windows user profile). In addition, I set a tempdir
option as well.
I've tried backing up another directory, and it seemed to work without a
problem. The main difference was the number and size of files. (The directory
that fails has more files and larger size files than the directory that
works.)
I also tried running the command a few times. Although it fails, it does
leave a partial backup that is recognized on subsequent runs, so that at least
is good.
After a few runs, I was finally able to upload the whole set. So, I'm happy.
Essentially, the program quits prematurely and needs a restart.
I realize now that the problem seems to be that pexpect.py tries to close a
child process (line 150). Maybe for some reason, the process is already closed
without pexpect noticing?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25138>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/