sbackup lock not stored in /var/lock

[John Willauer]

Binary package hint: sbackup

When I run sbackup it would not execute for several days.

After setting up cron to send me e-mail when executed, received e-mail stating "Another Simple Backup daemon already running: exiting"

I found an form posting for this message at: http://www.ubuntuforums.org/archive/index.php/t-220996.html

The forum posting reported that "...problem was caused by a lock file left over in /root."

After examining the sbackup source code, I discovered that this poblem was caused by the location of the lock being redefined. In sbackupd "lockfile" is initialized to point to /var/lock/sbackup.lock. Loading the sbackup config file resets "lockfile" to point to the current default directory by not explicitly pointing to /var/lock/sbackup.lock.

Thus when sbackupd is executed by root the current directory is /root, thus the lock is set in /root.

[C de-Avillez (hggdh2)]

Indeed I see sbackup locks at least under /root and /var/run. End result is sbackup fails.

[mNeo (maverickneo)]

I also see the lock files left in /root which stop sbackup from running. So I had to add an extra cron entry to specifically remove this lock file every day 10 minutes before the sbackup starts.

[Oumar Aziz OUATTARA (wattazoum)]

This has been fixed upstream . with the new version :
- if you still have the "lockfile " in sbackup.conf set to "sbackup.lock", the behaviour won't change but we are making sure of testing if the lockfile is valid. If not we delete it.
- if you delete the "lockfile" line in sbackup.conf , the lock file will go to /var/lock/
- for a fresh install , there is nothing to do (the lockfile is set to /var/lock/sbackup.lock )

[Oumar Aziz OUATTARA (wattazoum)]

If you want to test and confirm that it has been fixed , here is a file to install

[C de-Avillez (hggdh2)]

sbackup 0.10.4beta3 seems indeed to have resolved this issue.