Duplicity

If lockfile is not released on crash, subsequent backups fail

Asked by grimborg

I've recently had a problem where duplicity failed and didn't delete lockfile.lock, so the subsequent backups also failed, until I manually removed the file (after verifying that duplicity was not running).

Is there any way to prevent this issue in duplicity?

I'm running duplicity 0.6.24 with duply 1.5.5.5

Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kenneth Loafman (kenneth-loafman) said : 		#1

At the moment, no. Please use the "Create bug report" link above the Message box to create a bug report from this question. That will preserve this note.

In order to do this we would need to go to a timed lockfile and refresh the timer on a regular basis, similar to a built in watchdog function. There are hazards in this if the users system is slow, so consider the tradeoffs.

Revision history for this message
grimborg (grimborg) said : 		#2

Can't we use flock instead of storing the time in the lock file, or am I missing something?

Revision history for this message
Kenneth Loafman (kenneth-loafman) said : 		#3

That's a possibility. I would require one additional file id, but would solve the problem.

Can you help with this problem?

Provide an answer of your own, or ask grimborg for more information if necessary.

To post a message you must log in.