Rejected posting to ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
You are not authorized to send mail to the ADVANCED-DOTNET list from your rsync@LISTS.SAMBA.ORG account. You might be authorized to send to the list from another of your accounts, or perhaps when using another mail program which generates slightly different addresses, but LISTSERV has no way to associate this other account or address with yours. If you need assistance or if you have any question regarding the policy of the ADVANCED-DOTNET list, please contact the list owners: [EMAIL PROTECTED] ---BeginMessage--- The original message was received at Tue, 9 Aug 2005 09:51:05 +0100 from lists.samba.org [40.92.149.239] - The following addresses had permanent fatal errors - advanced-dotnet@discuss.develop.com === This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com ---End Message--- -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Automated reply from [EMAIL PROTECTED]
On holiday -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
meta data stored in separate file?
i found a couple messages in the archives relating to backups vs. distribution and ownership issues without root privs that kinda touched on the idea of storing meta info (ownership, modes, acls) in a separate file. has anyone else looked at storing meta data in a side file of some sort? it seems that it could be done all on the client side. send over files with totally plain meta info and then send another file with text containing the actual meta data. the reason i'm looking at this is to use rsync as a backup system for foreign systems. ones that don't share uid space (or even os similarity) to the central server. basically use ssh with a non-root keypair so that data can be read/written to each servers backup space. by using separate meta files, we can handle windows or other systems that might have acls or permissions flags that don't match with unix. i realize that this is normally what tar/cpio/dump/etc would be used for, but rsync has the nice ability to use hardlinks to create pseudo snapshot backups that make it easy to retrieve things, plus the inherent speedup from the rsync algorithm. any input from the list about this idea? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: meta data stored in separate file?
On Tue, Aug 09, 2005 at 12:52:43PM -0700, Joe Pruett wrote: has anyone else looked at storing meta data in a side file of some sort? I recommend using a program such as fakeroot (when used with the -s option to save the meta data) or pretendroot (which I haven't personally used). For instance, either run something like this for a daemon setup: fakeroot -s /path/fakeroot.data rsync --daemon --port=8873 \ --config=/path/rsyncd.conf (Make sure that the real user that is running the daemon can write to the lock file, the pid file, all the module paths, and any log file; also, disable chroot and be sure to use an unprivileged port.) Alternately, do something like this for a remote-shell-based copy: rsync -av --rsync-path=fakeroot -s /path/fakeroot.data \ /src/ host:/dest/ Either option will allow the remote rsync to save all the owner, group, device, etc. info that the sending rsync provides. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: meta data stored in separate file?
I recommend using a program such as fakeroot (when used with the -s option to save the meta data) or pretendroot (which I haven't personally used). For instance, either run something like this for a daemon setup: fakeroot -s /path/fakeroot.data rsync --daemon --port=8873 \ --config=/path/rsyncd.conf but this doesn't work for windows acls, and maybe not for unix acls. it also wouldn't apply to apple fork data, which was another thread i found but forgot to mention in my message. i realize this is turning rsync into more of a backup system than it is now, which is why i was thinking maybe it could be done with client side code. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: meta data stored in separate file?
There's something called backuppc (i think backuppc.sourceforge.net) which uses some sort of db backend and has multiple possible transports, rsync is one option. I think it might do what you're looking for. It also has other interesting features, like storing only a single local copy (on the backup server) of a given remote file. So you don't, for instance, have an entire windows XP image on disk for each client, but rather many database entries for files with these names md5sums. I haven't really used it (yet). I don't think it directly supports mac resource forks, perhaps could be made to do so with an appropriate rsync variant. On Tue, Aug 09, 2005 at 01:58:47PM -0700, Joe Pruett wrote: I recommend using a program such as fakeroot (when used with the -s option to save the meta data) or pretendroot (which I haven't personally used). For instance, either run something like this for a daemon setup: fakeroot -s /path/fakeroot.data rsync --daemon --port=8873 \ --config=/path/rsyncd.conf but this doesn't work for windows acls, and maybe not for unix acls. it also wouldn't apply to apple fork data, which was another thread i found but forgot to mention in my message. i realize this is turning rsync into more of a backup system than it is now, which is why i was thinking maybe it could be done with client side code. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html danno -- dan pritts - systems administrator - internet2 734/352-4953 office734/834-7224 mobile -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: meta data stored in separate file?
There's something called backuppc (i think backuppc.sourceforge.net) which uses some sort of db backend and has multiple possible transports, rsync is one option. I think it might do what you're looking for. interesting tool, but it is not what i need. it doesn't do acls. it is a pull system, rather than push. this is for an isp setting (which i didn't mention yet) where colocation customers would push their backups to a central box. any other tools out there? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
