OK, thanks. Marking bug as invalid.
For future reference, I think it is a bad idea to have two different
schedules and/or users back up to the same backup location, and it
actually seems to be not supported. It would be nice if this was
signalled and reported back to the user in a more transparent way.
Off-topic, gnome-schedule is a graphical front end for user cron jobs.
Likely, that cron job still persists, verify with 'cron -l', and check
further actions with 'man cron' ;-)
** Changed in: sbackup
Status: New => Invalid
--
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to sbackup.
https://bugs.launchpad.net/bugs/1087872
Title:
Backup to Remote PC Freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/sbackup/+bug/1087872/+subscriptions
_______________________________________________
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
