\t\t\t\tNota Bene \/ before:<\/p>\n
The Synology system provided rsync is not for me. It’s somehow modified and spoilt.<\/p>\n
Well, it’s not only me experiencing weird effects with the “built-in” rsync. And I think, quite a few of the answers to that forum article do not quite fit at all.<\/p>\n
The details of the case:<\/p>\n
I mainly followed the “German Synology wiki” on IPKG<\/a>. (As anxious as I am, I do keep a backup of that article at \u2026\/com\/synology-wiki.de\/ . Yes, I do have an idea, that this step alone is rather in vain.) Then I installed the rsync package provided by IPKG.<\/p>\n An entry for \/etc\/rc.optware got created in \/etc\/rc.local, and they suggest to remove it, and I did that. Now my only minor problem with the “alternative rsync” is, that I have to specify the remote rsync on my local rsync command lines like this: “–rsync-path=\/opt\/bin\/rsync”. That’s a PITA, but that’s not too hard.<\/p>\n Update 2013-08-31:\u00a0en.wikipedia.org\/wiki\/Ipkg<\/a>\u00a0says IPKG was discontinued. en.wikipedia.org\/wiki\/Opkg<\/a>\u00a0is the follower,\u00a0code.google.com\/p\/opkg\/<\/a>, but it hasn’t really taken off.\t\t\t\t<\/p>\n","protected":false},"excerpt":{"rendered":" Nota Bene \/ before: This is the text, that helps me personally re-installing rsync, whenever it magically disappears, maybe caused by an DSM update. True, I should bring a little structure into this article. I never ever care about\u00a0rsyncd, as I am doing “rsync over ssh”; \u00a0any activity suggested regarding rsyncd does not concern me. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_share_on_mastodon":"0"},"categories":[255,397,575],"tags":[1177],"class_list":["post-292","post","type-post","status-publish","format-standard","hentry","category-ipkg","category-opkg","category-synology","tag-my_most_important_article_on_ipkg_for_synology"],"share_on_mastodon":{"url":"","error":""},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paO0kP-4I","jetpack_likes_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/posts\/292","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/comments?post=292"}],"version-history":[{"count":0,"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/posts\/292\/revisions"}],"wp:attachment":[{"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/media?parent=292"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/categories?post=292"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp.jochen.hayek.name\/blog-en\/wp-json\/wp\/v2\/tags?post=292"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nSo, well 1st I had to install IPKG itself.
\nMy CPU on the DS213+ is an e500 (actually: e500v2), so I went the e500 way in their description.<\/strong>
\n My CPU on the DS112+ is a “Feroceon 88FR131 rev 1<\/a> (v5l)”, there is a note on how to deal with the DS112+, pls follow that one.
\nMy CPU on the DS115j is a “Marvell<\/span> PJ4Bv7 Processor rev 1<\/a> (v7l)”, still a Feroceon, but a little hidden; the Feroceon check should be changed to check for Marvell instead; \u2026<\/strong><\/p>\n
\nI am not sure, it concerns me at all, as I mention “my” rsync on the NAS by full path on my command lines outside the NAS.<\/p>\n