Ok, it's more complicated. This is what I've figured out:
nssbackup checks for a running instance and does not start if an instance is
already running. However, during this start attempt the lock file of the first
instance is removed. A long running backup task does not recognize this (I
guess a full backup of your 60 GB would take 5..10 hours). Therefore, later
executions by cron are sucessful because no lock file is present.
** Changed in: nssbackup
Status: Incomplete => Confirmed
** Changed in: nssbackup
Assignee: (unassigned) => Jean-Peer Lorenz (peer.loz)
** Changed in: nssbackup
Milestone: None => release0.2
--
nssbackup does not prevent itself from running in parallel.
https://bugs.launchpad.net/bugs/573733
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
_______________________________________________
Mailing list: https://launchpad.net/~nssbackup-team
Post to : nssbackup-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~nssbackup-team
More help : https://help.launchpad.net/ListHelp
