Question #262087 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/262087
Kenneth Loafman proposed the following answer: Possibly. Read up on Python's signal handling. We have to know the path before we handle this, thus the questions. On Tue, Mar 3, 2015 at 9:56 AM, edso <[email protected]> wrote: > Question #262087 on Duplicity changed: > https://answers.launchpad.net/duplicity/+question/262087 > > edso proposed the following answer: > On 03.03.2015 14:21, Kenneth Loafman wrote: > > Question #262087 on Duplicity changed: > > https://answers.launchpad.net/duplicity/+question/262087 > > > > Kenneth Loafman requested more information: > > It's in the older pexpect module which uses SIGINT, SIGHUP, then finally > > SIGKILL to close the child process. I'm not sure what it would be > > trying to kill though. That's a bit of a mystery. > > > > still. if he's right and duplicity uses the last pexpect's return code > as global return code, that smells buggy. > > ..ede/duply.net > > -- > You received this question notification because you are a member of > duplicity-team, which is an answer contact for Duplicity. > > _______________________________________________ > Mailing list: https://launchpad.net/~duplicity-team > Post to : [email protected] > Unsubscribe : https://launchpad.net/~duplicity-team > More help : https://help.launchpad.net/ListHelp > -- You received this question notification because you are a member of duplicity-team, which is an answer contact for Duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
