tenjaa

Members
  • Posts

    22
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by tenjaa

  1. @RomanZ

     

    I have to admit that I have (almost) no detailed knowledge about permissions in linux.

     

    To clarify:

    I have the standard folder "music". Users tenjaa, x and y have r/w-rights.

    As tenjaa is my main user, it want to sync this folder to a second synology as this user. The second one has the same users.

    Now only tenjaa can r/w the folder because he is the owner and the permissions from different users are not synced.

     

    Right?

  2. Hey,

     

    im using BTSync on Windows 8 and Synology 213j.

    The audiostation on Synology creates those "@eaDir" folders.

    I have already added them and restarted both devices but the folders are still transmitted.

    I am syncing the whole iTunes folder, so that you know how it looks like ;)

    Windows Version: 1.1.82

    Synology Version: 1.1.70

     

    My syncignore:

     

    # .SyncIgnore is a UTF-8 encoded .txt file that helps you specify single files, paths and rules 

    # for ignoring during the synchronization job. It supports ‘?’ and ‘*‘ wildcard symbols.
    #
    # Note that .SyncIgnore is applied only to the folder where it is contained and 
    # will not work with the files that have already been synced.
    #
    # If you add indexed files to .SyncIgnore, they will be deleted on other syncing devices. 
    # In order to avoid this:
    # 1. Quit BitTorrent Sync or remove the folder from sync on all the devices.
    # 2. Modify .SyncIgnore file on all of them so that it contains same info.
    # 3. Run BitTorrent Sync or re-add the modified folders.
    #
    #
    # OS generated files #
    .DS_Store
    .DS_Store?
    ._*
    .Spotlight-V100
    .Trashes
    Icon?
    ehthumbs.db
    desktop.ini
    Thumbs.db
    @eaDir
    *.jpg

     

     

    Bug? Feature? Am I stupid?

  3. -ROADMAP: I wish there would be a roadmap. There does not have to be an exact time like next week there will be this etc. but maybe this feature hast high priority, this one less, this one wont be included.

    -VOTABLE WISHLIST: I guess many people are afraid to post over and over again the same feature requests. So why not make them votable. Something like: http://goo.gl/FvkKqR (Chromium Issue List).

  4. LInux ARM 1.1.48 on Raspberry Pi takes years to re-index.

    Hello,

    I updated my Raspebrry Pi from 1.1.42 to 1.1.48. After rebooting the indexing seems to be stuck.

    I see no "(Indexing...)" and the data already indexed also does not change when I reload the webgui after a while.

    For now it indexed less then 10 MB in 3 of 6 shares from a total of around 100 GB data, but it does not go on.

    Anyone having the same problem or a solution for me?

    Ill send an email with the debug to the devs later if it is not a problem caused from me.

    Edit: Everything is indexeded now, except my iTunes folder. Maybe that index got currupted? But it is uploading now this folder and everything is fine then again (I hope).

    @Devs: should I still send you a debug log of all this?

  5. HDD spindown: take a look here: http://forums.storag...-bad-for-drive/ its a forum for storage specially ;) furthermore google made a study but i dont remember the results

    they say if you spin it down severel times (some say 10, others 100) it's fine. you must look if you only sync once per week you should spin it down for powersavings

    Speed on Lan: 6GB iso -> 2.4 MB/s from SSD of my computer to an external 2.5HDD from the RPi

  6. This is normal - but it does cause a great deal of confusion for users! It can often take several days/weeks before new builds are pushed out via auto-update. If you don't want to wait, you can always manually grab the latest build here: http://forum.bittorr...ync-build-1142/

    Are you a dev?! Just a question cause youre posting so much here :)

    But even if not I need to correct this: Auto-update didnt say there is no update, instead there was an update displayed but it failed downloading it. So it was more a network error at bittorrent.com. But 5 minutes ago it worked again as intended. ;)