I'm loving TC 3.1, but eventually everyone has to log out. The "safe" backup option is a wonderful innovation.
My first few tries produced a non-shutdown, explained by an error message referring to some file in /tmp that does not exist. (Sorry, I forgot the name. Something like /tmp/backup_errors.) The error messages show up in /tmp/wm_errors instead. Reconciling the error message with the actual behaviour should be comparatively easy, but still worthwhile.
My backup+save failed because the script didn't have permission to create a new file in the backup directory. It seems like "mydata.tgz" is owned by "root:root", whereas the backup "mydatabk.tgz" is owned by "tc:staff". Could somebody double-check the flow of permissions as the script runs? I think the operation of backing up the previous mydata.tgz should be done by root also, so this problem can't happen. (I worked around it by relaxing the permissions on the directory holding my backup files, but that's rather inelegant.)
Thank you.