Re: name too long problem?
On Wed, Feb 15, 2012 at 6:21 AM, Carlos Carvalho car...@fisica.ufpr.brwrote: filename overflows max-path len by 1: path Count the characters in the displayed path and you'll see what the max_path value is. That message is output by the sender, and indicates names that are too long to put into the stream of file-list data. Since rsync currently uses paths from a single chdir, you cannot send files that overflow the OS's max-path limit when referenced by the in-transfer path + filename. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Support for a (new?) backup concept
I've had an idea for a backup concept that could be new, or at least I have not been able to find anything similar on the net. It's something like a reversed rsync, although this term is already commonly used for backup restoration. The goal is to get the best of both pull and push backup methods. Let the client have some data to be backed up to the server. The client is granted key-based ssh login to the server, with a command=rsyncwrapper directive (ssh forced command) in an authorized_keys file. This wrapper on the server essentially launches an rsync session in client mode which expects stdin/stdout to be already connected to a remote shell (on the client machine, through the very same ssh connection), and uses it to launch an rsync in server sender mode (on the client machine) and talk to it. Here are some characteristics: - The rsync client on the server can rather safely be run with root privileges and thus make very exact backups (pull). - Given that the wrapper script on the server is not completely broken, it's not possible for malicious code on the client to destroy its own backups (pull). - Different clients with name or uid clashes in the backup files do not interfere as their data can be guaranteed to be stored in different directories (pull). - The backup session is initiated by the client (which does not prevent the server from comfortably posing some restrictions on the frequency or time of backups), which makes for a great deal of flexibility. This also avoids possible NAT problems for mobile devices (push). The setup is generally rather decentralized, which is A Good Thing. - No client needs to run an ssh server. - This method's safety concerns are the same as with the pull method, minus the need for an ssh server on the client (Instead we need one on the server, but it is there in most cases anyway). For the client, it is painless to deploy a restricted shell that will only run an rsync --server --sender ..., and client safety can further be improved by lowering the privileges of the shell receiving this commandline. - Configuration of backup behaviour remains comfortable at least to some degree (and non-statical, per-session) because the client can provide commandline arguments to the forced command which the wrapper script then only needs to allow / translate. I'm currently a running very similar setup, using a wrapper script that calls rsync with an -e fake remote shell option. This fake shell does only redirect its stdin/out to/from named pipes on the server, and a second ssh connection from the client connects those fifos to a local shell. However, it would be a much more elegant solution to have an option to rsync that makes it assume being already connected to a remote shell via fd 0/1. From a look at the rsync code, I think the feature could be integrated, although with some special handling (stdin/out should be dup'ed to other fds and then closed before any of the debug/error/verbose printing to stdout occurs. Perhaps what is normally printed to stdout could be optionally written to a logfile. The rsync -- server commandline which is normally appended to a remote shell commandline must instead be written to stdout). I would like to know what you generally think of this concept, and if you think integration of some support code would be worth a try -- or would the setup complications and the additional cruft in the code outweigh the merits for most users? Or has anyone heard of similar approaches, or ones that achieve the same with less complications? Please excuse the long input / thanks for reading / hoping to receive answers! -Jens Stimpfle -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Fwd: Re: cwRsync got killed...
A bit late, but someone (anonymous) provided a link to download. the md5 is correct, it matches the last sourceforge state. And the md5 and sha256 mentioned at https://www.itefix.no/i2/node/12862 - before he gave up the project. MD5 c787dfa854775793d1a1b5c3502b57b5 sha256 5abeec588e937bd749456ddb347e4116b0f8407e15f412281fc64c763d1de62d For obvious reasons you should check the md5 / sha256 after downloading, the file might change without notice : ) . Content looks good and original, so it is original (with a very high probability). Side question: Does anyone know the probability of generating a file with the same md5 and sha256 which is still looks valid with the expected content (including the manually unpacked nullsoft installer inside the zip)? Jou Original-Nachricht Betreff:Re: cwRsync got killed... Datum: Thu, 16 Feb 2012 16:43:29 +0200 Von:John Doe **@gmail.com An: Joachim Otahal (privat) j...@gmx.net Real name? No, it's not, obviously. For some reason I couldn't post this on the rsync forum, where I found your request. Would you, kindly, consider adding the link there? On Wed, Feb 15, 2012 at 10:41 PM, Joachim Otahal (privat) j...@gmx.net mailto:j...@gmx.net wrote: John Doe schrieb: I still have the cwRsyncServer_4.2.0_Installer.zip file. I've uploaded it here: http://www.2shared.com/file/212w-aDp/cwRsyncServer_420_Installer.html Thanks. Is this your real name? kind regards, Joachim Otahal -- Please use reply-all for most replies to avoid omitting the mailing list. 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: Fwd: Re: cwRsync got killed...
AGH ! I postet the wrong checksums, I posted the ones for cwRsync_4.2.0_Installer.zip instead of cwRsyncServer_4.2.0_Installer.zip cwRsyncServer_4.2.0_Installer.zip: MD5: c787dfa854775793d1a1b5c3502b57b5 SHA-256: 21e608caed9e5e7e1f1f9881729eab0a8fce6e1ff31d85dcb7759d502478160c The checksums are still right. Jou Joachim Otahal (privat) schrieb: A bit late, but someone (anonymous) provided a link to download. the md5 is correct, it matches the last sourceforge state. And the md5 and sha256 mentioned at https://www.itefix.no/i2/node/12862 - before he gave up the project. MD5 c787dfa854775793d1a1b5c3502b57b5 sha256 5abeec588e937bd749456ddb347e4116b0f8407e15f412281fc64c763d1de62d For obvious reasons you should check the md5 / sha256 after downloading, the file might change without notice : ) . Content looks good and original, so it is original (with a very high probability). Side question: Does anyone know the probability of generating a file with the same md5 and sha256 which is still looks valid with the expected content (including the manually unpacked nullsoft installer inside the zip)? Jou Original-Nachricht Betreff: Re: cwRsync got killed... Datum: Thu, 16 Feb 2012 16:43:29 +0200 Von: John Doe **@gmail.com An: Joachim Otahal (privat) j...@gmx.net Real name? No, it's not, obviously. For some reason I couldn't post this on the rsync forum, where I found your request. Would you, kindly, consider adding the link there? On Wed, Feb 15, 2012 at 10:41 PM, Joachim Otahal (privat) j...@gmx.net mailto:j...@gmx.net wrote: John Doe schrieb: I still have the cwRsyncServer_4.2.0_Installer.zip file. I've uploaded it here: http://www.2shared.com/file/212w-aDp/cwRsyncServer_420_Installer.html Thanks. Is this your real name? kind regards, Joachim Otahal -- Please use reply-all for most replies to avoid omitting the mailing list. 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: Just delete extraneous files, without updating other changes?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You want --ignore-existing On 02/16/12 20:36, Bryan Pliatsios wrote: Hello all, I thought --recursive and --delete-before might be an option and I can quit rsync when it begins the updates, but the incremental recursive scanning is disabled and this will certainly crash rsync as it was before moving to v3.x (too many files). I have no experience with --write-batch but I wonder if it's safe/sane to edit the resulting batch output file, or by doing a --dry-run | grep deleting and fire that list thru rm. Other thoughts? Bryan - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk89s6sACgkQVKC1jlbQAQfZ2gCeNF+zLk0NOBB8F61Ti2wiOpc6 nK8Anj1Lc9LjFCuH2Moy0/veW/K0S6wg =f7dr -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. 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: Just delete extraneous files, without updating other changes?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually, you want --delete --ignore-non-existing and --ignore-existing On 02/16/12 20:55, Kevin Korb wrote: You want --ignore-existing On 02/16/12 20:36, Bryan Pliatsios wrote: Hello all, I thought --recursive and --delete-before might be an option and I can quit rsync when it begins the updates, but the incremental recursive scanning is disabled and this will certainly crash rsync as it was before moving to v3.x (too many files). I have no experience with --write-batch but I wonder if it's safe/sane to edit the resulting batch output file, or by doing a --dry-run | grep deleting and fire that list thru rm. Other thoughts? Bryan - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk89tBkACgkQVKC1jlbQAQdE6wCg/F82Wtqgg0dbJCGW0HJfDQ4n UkQAoOprJehXSe6Wc5x1x/gP8ENAHJSX =huox -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. 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: Just delete extraneous files, without updating other changes?
Kevin, thanks so much, I should have read the man page closer: --existing, --ignore-non-existing This tells rsync to skip creating files (including directories) that do not exist yet on the destination. If this option is combined with the --ignore-existing option, no files will be updated (which can be useful if all you want to do is delete extraneous files). I'm really embarrased. Thanks for not rtfm-ing me. Bryan On 17/02/2012, at 12:57 PM, Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually, you want --delete --ignore-non-existing and --ignore-existing On 02/16/12 20:55, Kevin Korb wrote: You want --ignore-existing On 02/16/12 20:36, Bryan Pliatsios wrote: Hello all, I thought --recursive and --delete-before might be an option and I can quit rsync when it begins the updates, but the incremental recursive scanning is disabled and this will certainly crash rsync as it was before moving to v3.x (too many files). I have no experience with --write-batch but I wonder if it's safe/sane to edit the resulting batch output file, or by doing a --dry-run | grep deleting and fire that list thru rm. Other thoughts? Bryan - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk89tBkACgkQVKC1jlbQAQdE6wCg/F82Wtqgg0dbJCGW0HJfDQ4n UkQAoOprJehXSe6Wc5x1x/gP8ENAHJSX =huox -END PGP SIGNATURE- -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html Bryan Pliatsios Senior System Administrator – wellcom group headquarters P +61 3 9946 8000 | M 0418 992 775 E bryan.pliats...@wellcom.com.au | W http://www.wellcom.com.au wellcom group limited 870 lorimer street port melbourne vic australia 3207 Please consider our environment before you print this email IMPORTANT INFORMATION __ This correspondence is for the named person's use only. It may contain confidential or legally privileged information or both. No confidentiality or privilege is waived or lost by any transmission error. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any opinions expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the opinions of Wellcom Group Limited. Neither the sender nor Wellcom warrants that any communication via the Internet is free of errors, viruses, interception or interference. Information is distributed without warranties of any kind. __ -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
