adam1v

Members
  • Posts

    50
  • Joined

  • Last visited

Posts posted by adam1v

  1. On 8/19/2019 at 5:14 PM, kos13 said:

    Recently we went thru some organizational changes and internal tools adjustments, and this affected the speed we respond to the forum posts and support tickets. We are working to resolve the situation as soon as possible. I hope the situation will normalize in a couple of weeks. 

     

     

    Judging by the lack of staff forum posts and delays in responding to tickets, I read the above comments as a number of staff have been laid off :(

  2. Thanks for this, I have added the group, however it did not allow me to address a problem I having:

     

    I have a DS415+ which has a shared folder which allows read/write access for ~10 users over the LAN.  Offsite I have a DS214play where the same folder in synced with BT sync.  In addition there is one laptop that uses BT sync to stay in sync with the server from remote locations.

     

    In the main everything works as expected, however any files/folders which are generated from the laptop and as such are created by the BT Sync user on either synology are read only for all the other users.  Obviously all the users concerned have read/write access to the sync folder. 

     

    The only way around this that I have found is make all users a member of the admin group and then restrict their access on a per folder basis.  Clearly this is not a great solution, so if anybody knows what can be done about this that would really help.

     

    After following the instructions on this thread I can now modify the permission of the synology group, but adding users to this group does not solve the problem.

     

    We have exactly the same issue, except you cannot add domain users to the admin group. So no work around for us....

  3. It was an interesting discussion a while back, but let me explain why it wasn't solvable in 1.x releases. First of all you will need to synchronize file uid/gid together with permissions. Which might be fine, if there are two machines that are owned by you and you are guarantee that users/groups are identical between these machines. Majority of users will not be able to do that and this will lead to a complete mess. And keep in mind Linux -> Win/MAC synchronization. 

     

    This was simple usability problem, rather than technical. 

     

    kos

     

    Hi Kos, are you suggesting this has been resolved with 2.x?

  4. welcome to the bane of my life right now.... please see:

    http://forum.bittorrent.com/topic/31047-qnap-file-permissions-can-not-resolve-using-normal-methods/

     

    http://forum.bittorrent.com/topic/31301-btsync-14-on-synology-nas-official-package/

     

    For now, it seems the developers took a conscious decision not to replicate permissions, thus they will replicate your files but prevent you from editing them.

     

    I really hope they sort this out as a priority, its hugely detrimental to the software IMO. 

  5. I have raised these issues with a number of BTSync developers/moderators and even some were surprised that the (intended) bug exists.

    I'm amazed that the BTSync software has been developed to intentionally not copy permissions when syncing new files. Surely it's a fundamental flaw that if users cannot open/modify the copied file then there is no point in using this software?

    Hopefully if enough people voice their concerns it might get addressed?

  6. The problem is, we don't have access to the BTSync app user settings (at UI level), therefore, we cannot add the user account in which the app runs to the same group, otherwise Id create a new group, add the BTSync user to this + all my active directory users and apply that permission at the top level folder.

     

    In addition, the folder that contains this file has RW permissions for everyone, its just BTSync that's not applying the RW permissions :(

     

    Any further input you can add is greatly appreciated...

  7. @Tenjaa

    I have been trying to raise this issue with Synocommunity here: https://github.com/SynoCommunity/spksrc/issues/1243

    As an end user, we have very little control over how the package/application is ran, we are not able to select the user account or group it is started with.

     

    In your example, if your are using it between NAS devices, BTSync actually takes ownership of the file, using its own account, which appears to be called BTSync, but this is not created by the user, it appears to be a system/unix account created with the app, 

     

    A6HfJT.jpg

     

    In my example above, the left side has the original file and the right side has been replicated. No users have write access :(

     

    This might be by design, but surely its quite a big fundamental flaw if users cannot edit or modify the replicated files?