Andy+
-
Posts
584 -
Joined
-
Last visited
Posts posted by Andy+
-
-
Depending on the OS on your PC you find a working folder, in which files like *.db and *.db-wal are stored. Stop Resilio and delete such files and start again. Then a new indexing is starting.
-
Regarding the confusion of the DSM 7 permissions (root/user) during the installation process I got today the follow message from Synology:
Start
Yes, you may continue using root privilege ONLY if you apply a token from us to bypass the lower privilege setting this time round, without which, your package installation would fail in DSM7.0 Beta.
As mentioned in point 2 in my previous email:
To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology.
In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center.
To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation.
If you wish to continue running as root rather than user, please follow the instructions below:
i) Log in to the DSM of NAS device(s) that you want to develop / test on
ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat”
iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.)
iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/
v) You are all set to develop the new version using your current privilege level setting.
Our ultimate goal is still hoping for all of our package developers to be able to abide by our new privilege setting in future versions.
End
I try to install the related Resilio package with the following message:
-
If nobody can help, best to contact Support directly:
https://help.resilio.com/hc/en-us/requests/new?ticket_form_id=91563
-
Even though you log in?
-
Doe you use version 2.6.4 from Google platform? Which Smartphone you have and Android version? Are the peers connected in a good condition and environment with good perfomance?
Maybe a permission problem.
-
This kind of support is usual here. Maybe use Syncthing, if nothing runs. But unfortunately there is no ready installation package, maybe look at package center of QNAP, but surely is a old version and you can update to current v1.9.0
-
I think, is time for update
-
I´m in touch with Synology and got today the follow message about current version of third-party packages would be incompatible:
Thanks for your continuing interest in developing with Synology. We are planning for a major version update to DSM7.0 Beta soon. Due to DSM 7.0 having quite a few adjustments to the framework, current version of third-party packages would be incompatible with the new DSM 7.0 version. Hence, we are providing you with a new set of Developer's Guide, Toolkit and relevant resources, so that your future package can be compatible with our upcoming DSM release. DSM 7.0 Package: Please provide us with your Synology Account (E-mail) before we can send you the portal url for downloading DSM7.0 Beta to your device. If you don’t have a Synology Account, please create one here: https://account.synology.com/ Let me briefly introduce to you the upcoming changes: Adjustment to lower the privilege level for third-party packages to run as a user rather than root. Package installation would fail if its privilege setting differs from our new requirement. To avoid future update issues, It is highly recommended that your package can be modified to match our new lower privilege framework. Please develop according to the new developer’s guide provided, and your users will still be able to carry out manual installation even if the package has yet to be approved and signed by Synology. In case of development time or technical constraints, we provided a tentative alternative for the benefit of existing third-party packages in our Package Center. To ensure that your current package remains functional in DSM7.0, you will be allowed to continue using the same privilege level settings for your new versions until further notice. However, you have to apply for an exemption token from us to be able to develop smoothly on your NAS device. Please note that your package will have to be officially approved and signed by Synology before your package can be released in our Package Center or to users for manual installation. If you wish to continue running as root rather than user, please follow the instructions below: i) Log in to the DSM of NAS device(s) that you want to develop / test on ii) Open Support Center → Support Services → Log Generation → Check “System” → Generate logs → Download “debug.dat” iii) Send this “debug.dat” to us by replying to this email (if you have more than one NAS device, please label the respective debug.dat clearly.) iv) We’ll then send you the token file (each token is only valid for one specific NAS device), for which you’ll have to rename it to syno_dev_token and place it under this location → /var/packages/ v) You are all set to develop the new version using your current privilege level setting. It is anticipated that a lot of Synology users will be upgrading to DSM 7.0 Beta after its public release. In order to make it in time with our DSM 7.0 Beta’s release, please submit your new version by the end of October 2020. For which, our package verification process will begin in October. Although you can continue to support the current DSM version, it is recommended that your package supports DSM 7.0 as a priority. Please refer to the package review items stated in Appendix C of the Developer’s Guide for an idea on the things to look out for to expedite the verification process. Thank you! -
-
If you read the comments in Google for the Smartphone APP, the problems are very similar:
-
The question is, if you have anything changed in the work load, it means more files, peers etc. Otherwise maybe went back. With v2.7.2 on all my devices I have no problems, but if I follow the threads here it seems v2.7.2 have some bugs.
-
No, unfortunately not. In the general forum there is always a hint about the development, e.g.:
However, the update cycles are quite long (too long! 😎), so that it is sufficient to check every months, or weeks for the not so patient 😇.
-
First of all, it has to be said that Syncthing is a tool more for technicians. It surely has some goodies in the GUI, but something like ticking autostart, that's too much of a diva for that. Nevertheless, there is an entire website in the documentation for autostarting on various platforms.
It is not true that the GUI of Syncthing is not being optimized, it just has not fundamentally changed. But that is also not the case with Resilio. The difference between BTsync v1.4.111 and Resilio v2.7.2 is visible, but this is also the case between Syncthing v0.10 and v1.8.0.
NAS clearly fall short. Syncthing has for Synology its own APP which works perfectly and is always up to date. Other NAS brands will probably come with time. The ones for Synology comes from Kastelo and as I know Kastelo owned Syncthing as a brand.
The actual synchronization is almost as fast with nothify as with Resilio. Since several years I have both tools on 4 Synology's, 4 Windows computers, 3 Android smartphones and can say so much. Resilio's community policy has allowed Syncthing to catch up and that's a very, very unfortunate. Today Syncthing is just as good as Resilio in terms of core functionality.
One thing has to be understood: Resilio is peer-oriented, Syncthing is device-oriented and that is a fundamental difference in concept and in the follow in operation and administration. Once you understand that, some things are easier.
Resilio is still the first choice for me. This also in the future when the update cycles get better or shorter and when the community and license holders are no longer neglected.
-
-
Goodsync and Resilio (same issue for Syncthing) are different in some feature points. Goodsync is not a P2P software as Resilio, is more a very good automatic FreeFileSync, I mean that with simple words. To have a view to your points, so
- is answered
- is not implemented now. If you want, use Syncthing, which have in the Peer settings of the GUI a window for that.
- Normally each 600 sec. you have a new indexing. Otherwise use Powersettings.
-
Resilio wastes great potential, that's the users.
We are in a similar community here, whether licenses have been bought or not. And users like to test too. With this, software can be developed much faster, better and more efficiently than without it. That's why Syncthing has gotten so good so quickly. Nobody does that with professional corporate customers, they expect something for the money.
It is foreseeable that Resilio will be left behind, as there is also work on features etc. and the defectors there will also ask for selective sync etc. or suggest this as a feature request.
-
I can understand that capacities have to be used carefully. But Resilio has a crisis of confidence in relation of the users. I keep seeing new users in the Syncthing forum who come from here frustrated. Anyone who asks qualified questions there will be looked after by at least 3 maintainers or software developers and, if necessary, further contributors. Nothing really works here in the Resilio Forum, just announcements and promises, but ultimately far too little is happening. I do not understand that.
I can testify that Syncthing still has its small bugs, but now runs just as well as Resilio. Resilio has approved all of this itself and if you don't necessarily need the special features such as selective sync, local copying, simple sharing, you have a very simple choice and alternative and it works perfectly and basically just as quickly. And (!) Is free (!)
And I say that as a user with several licenses.
-
I got no reaction from any member of Resilio. I dont understand that.
-
Maybe went back to v2.7.1 or v2.7.0, since it could be a bug.
-
I got no reaction from any member of Resilio. I dont understand that.
-
I got no reaction from any member of Resilio. I dont understand that.
-
For different reasons the people went back to version 2.7.0 (1366) to solve different problems, but no reaction from any member of Resilio. I dont understand that.
-
Maybe is better
On 7/23/2020 at 7:11 PM, Thomas P. said:my Synology DS415play against my Synology 414pro
Both DS have 1 GB RAM and a part of it is used by the system. So the question is, how much folders and files are managed from Resilio.
On 7/23/2020 at 7:11 PM, Thomas P. said:both had 1of1 peers, today it is 1of1 than 0of1 after a while 1of1, than 0of1
This is maybe more a performance problem of the network to the external Internet. If you have problems with the Internet connection, this could be the effect, since Resilio need the Internet connection to contact the peers between the different devices, even there are in the same LAN.
-
Latest desktop build 2.7.2
in Sync General Discussion
Posted
I think, at least is understood from all people. But what the people see regarding activities to solve Bugs and to have regular Updates etc. is another thing.