Hi Sean, Can you please setup backup for albatross?
I gave sudo permissions to the "jafo" user, which has the key j...@guin.tummy.com authorized. I think the policy now is that root logins to albatross are not allowed. So what might work is this: Create an rsyncbackup user, and give it sudo permission to run rsync (any command line arguments). Put your backup pubkey into rsyncbackup's authorized_keys. Could that actually work? albatross admins: would that be an acceptable setup? As for volumes to backup: I think /srv needs regular backup. Not sure about any of the others (and neither sure what your current strategy is wrt. volumes on the other machines). Compared to /srv, everything else is peanuts, anyway. Regards, Martin P.S. I have removed ~root/.ssh/authorized_keys. It only contained my key, and root logins are disallowed, anyway. P.P.S. You can stop doing regular backups to bag. I think we should keep the machine one for a little while, then turn it off and keep it around for a further while, and then return it to XS4ALL; making a complete dump before returning it. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
