[Rdiff-backup-bugs] [bug #27250] Feature Request: rdiff-backup should have a locking mechanism

[anonymous]

URL:
  <http://savannah.nongnu.org/bugs/?27250>

                 Summary: Feature Request: rdiff-backup should have a locking
mechanism
                 Project: rdiff-backup
            Submitted by: None
            Submitted on: Fri 14 Aug 2009 10:02:56 AM UTC
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Right now (with 1.2.8) if you start a backup and then pause/STOP (e.g.
Control-Z) it (or there is a network issue), and then start the same basic
backup command elsewhere, the second invocation detects the "failed" previous
backup and starts over again. If the first suspended process never comes back
then nothing bad happens. However, if it does come back, then it just
continues where it left off and you end up with a mess.

Now I realize this starting two instances is not a supported feature, nor
should it be, but there really should be some sort of a lock in place to
prevent occasional boneheadedness from screwing things up.

In cases where the rdiff-backup program is running on a server and attached
to non-network attached storage, UUCP style locks can work wonderfully
(exploiting atomicity of rename on *nix). For Windows, I think there is an
equally robust solution using directory creation. I know robust lock breaking
can be an issue and is imperfect, and network file systems (which I don't
personally recommend (just use SSH!)) complicate things. But I believe a
partial solution is better than non. If I can get around to this, and there is
interest, I might look into it.




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?27250>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/