Yet another update: Okay, maybe this is what had gone wrong before: The "test" function works without a colon, but the actual back up resulted in the following error. With the colon back in, the backup went ahead fine. Anyway, I'm just happy to know one option that works for what I'm doing (scheduled backups), and for me that is with a colon and a full path name.
Date: Sat, 14 Oct 2006 12:00:05 -0700 (PDT) From: Cron Daemon <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Cron <[EMAIL PROTECTED]> if [ -x /usr/sbin/sbackupd ]; then /usr/sbin/sbackupd; fi; I: Securing permissions at: ssh://cpbl:[EMAIL PROTECTED]/homegrad/cpbl/private/backup//2006-10- 02_12.00.09.708563.cpbl-laptop.inc Traceback (most recent call last): File "/usr/sbin/sbackupd", line 404, in ? upgrader.upgrade_target( target, purge ) File "/usr/sbin/upgrade_backups.py", line 60, in upgrade_target self.upgrade_tdir( target+"/"+adir ) File "/usr/sbin/upgrade_backups.py", line 78, in upgrade_tdir v = self.openfile( tdir + "/ver" ) File "/usr/sbin/upgrade_backups.py", line 307, in openfile return gnomevfs.open( uri, 1 ) gnomevfs.NotFoundError: File not found -- sbackup remote target fails https://launchpad.net/bugs/44260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs