Given your earlier announcement regarding the planned/necessary rebranding within the European Union, will this consequently be made available under the name “SeaDrive Drive client”?
(Maybe it’s better to replace “Drive” with “Share”?)
As this is a virtual directory which is not actually present on the computer locally, how do we get the files very first files into it? I mean…On android I used the client to access files, which were in the library because they were (and are) at first on one of my other clients locally.
This means if we use the SeaDrive for the very first time, I will have to copy (or better move?) one of my local directories (from one of my clients) into the virtual SeaDrive to build a new base library and then the files will be cached (where on this client?), thus still occupying the same amount of diskspace on this first client (because all files are coming originally from this client)? Will this cache then be released somehow somewhen for the sake of the the new concept (using seafile on clients with limited diskspace)?
Perhaps I simply have to try this new SeaDrive … but I have to wait for a stable Seafile 6 to upgrade my server (reliability reasons).
The 502 errors should be temporary if you can list the files in the client. 5.1.x server lacks of some necessary APIs used by the Drive client. We didn’t test it with 5.1.x server.
The space usage is a small bug of handling “unlimited” quota. It’ll be fixed in the next version.
Great news! When this works in Linux it might prevent running seafile server and client on my raspberry pi to have my Music-Libary locally on the pi to play music with mpd. WebDAV was not possible because the performance was to bad…
It’s not designed to do so. We think making only one account active at a time is more simplified. You can switch accounts and this should be enough for most use cases.
I started using Seadrive with server 6.0.3. I found a dozen of newly created folders on S: drive all with name like temp (*** are some random letters or numbers). They are all empty as well. Has someone else encountered the similar issue?
These libraries are created unexpectedly MSIb20bc.tmp, MSIb20f6.tmp
[09/01/16 21:08:55] get a new command: ("get-file-status", "S:/MSIb20bc.tmp")
[09/01/16 21:08:55] handleGetFileStatus: repo = "MSIb20bc.tmp" , path_in_repo = ""
[09/01/16 21:08:55] get a new command: ("get-file-status", "S:/MSIb20bc.tmp")
[09/01/16 21:08:55] handleGetFileStatus: repo = "MSIb20bc.tmp" , path_in_repo = ""
[09/01/16 21:08:55] get a new command: ("get-file-status", "S:/MSIb20bc.tmp")
[09/01/16 21:08:55] handleGetFileStatus: repo = "MSIb20bc.tmp" , path_in_repo = ""
[09/01/16 21:08:55] get a new command: ("get-file-status", "S:/MSIb20f6.tmp")
[09/01/16 21:08:55] handleGetFileStatus: repo = "MSIb20f6.tmp" , path_in_repo = ""
[09/01/16 15:23:48] seadrive.c(429): Starting SeaDrive client 0.1.0
[09/01/16 15:23:48] seadrive.c(453): rpc server started.
[09/01/16 15:24:08] sync-mgr.c(356): Repo 'MSIb20bc.tmp' sync state transition from 'synchronized' to 'committing'.
[09/01/16 15:24:08] sync-mgr.c(2067): All operations of repo MSIb20bc.tmp(7bcff1b4) have been processed.
[09/01/16 15:24:08] sync-mgr.c(356): Repo 'MSIb20bc.tmp' sync state transition from 'committing' to 'synchronized'.
[09/01/16 15:26:53] file-cache-mgr.c(1004): Read cache file C:/Users/71349/seadrive/data\file-cache/e3f412d1-895d-4b07-a654-d4daa02b3c80/My Photos/Camera/VID_20160519_234414.mp4 timeout.
[09/01/16 15:28:10] sync-mgr.c(356): Repo 'MSIb20f6.tmp' sync state transition from 'synchronized' to 'committing'.
[09/01/16 15:28:10] sync-mgr.c(2067): All operations of repo MSIb20f6.tmp(56c8b39e) have been processed.
[09/01/16 15:28:10] sync-mgr.c(356): Repo 'MSIb20f6.tmp' sync state transition from 'committing' to 'synchronized'.