[Bug 82992] sbackup lock not stored in /var/lock

[John Willauer]

Public bug reported:

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.

** Affects: sbackup (Ubuntu)
     Importance: Undecided
     Assignee: Ubuntu Desktop Bugs
         Status: Confirmed

-- 
sbackup lock not stored in /var/lock
https://launchpad.net/bugs/82992