search for: animeglob

Displaying 5 results from an estimated 5 matches for "animeglob".

Did you mean: animeglobe
2001 Dec 19
3
RSYNC: Backup Solution thoughts...
>I'm thinking of how to backup an entire server ("server A") to a >remote area ("server B") using rsync. > >My initial thought was to have a shell account on server B, then have a >cronjob running as root on server A that uses rsync to send all the files >over to the shell account on server B. > >Then I thought that this is not reliable against
2001 Dec 30
2
--owner --group without root access?
Is there a way to preserve the owner and group permissions without having root access? Well, this is not possible on the filesystem level of course, but what about storing the owner/group information in a supplementary file that can be read by rsync to later reconstruct this information? I'm using rsync to perform a server-to-server backup of a machine's hard drive. If the hard drive
2001 Dec 30
1
--backup-dir confusion
With the following rsync settings: cd /home/lina_backup rsync -R -v -z -rlptgo --delete \ --password-file=password \ --include-from=include --exclude="*" \ --backup --backup-dir=./`date -d yesterday +%Y-%m-%d` \ rsync://root@lina/backup current I would expect the backup directory to be /home/lina_backup/2001-12-29. But it becomes /home/lina_backup/current/2001-12-29. Is this a
2001 Dec 30
1
"hosts allow" secure?
How secure is "hosts allow"? I have "hosts allow = bkup" in my rsyncd.conf. Then in /etc/hosts I have: 64.29.16.235 bkup This makes only 64.29.16.235 able to connect to rsync. Could someone spoof their hostname somehow to trick rsync into letting them in, though? e.g. If they reverse DNS says that they're called "bkup".
2002 Jan 10
1
Error message when a file moves in the middle
I have a nightly cronjob that uses rsync to back up the files on another machine. Sometimes, I see error messages like this: send_files failed to open usr/home/setsuna/Maildir/new/1010573771.27924.lina.aaanime.net: No such file or directory It seems that the file existed at the moment rsync started, but as it was running that file (it's a file that stores an e-mail message; presumably the