for both @scheff and me, the SeaDrive Client only works for the actual first time we run it.
All successive runs fail with:
SeaDrive exited unexpectedly
And the console output is
fusermount: failed to chdir to /uni-mainz.de/homes/schlarbm: Permission denied fusermount: failed to chdir to /uni-mainz.de/homes/schlarbm: Permission denied (seadrive-gui:19057): Searpc-WARNING **: pipe client failed to connect to server: Connection refused
[10.04.2017 12:44:08] loaded 0 accounts [10.04.2017 12:44:08] seadrive gui started [10.04.2017 12:44:08] starting seadrive daemon: seadrive "-d" "/uni-mainz.de/homes/schlarbm/.seadrive/data" "-l" "/uni-mainz.de/homes/schlarbm/.seadrive/logs/seadrive.log" "-f" "/uni-mainz.de/homes/schlarbm/SeaDrive" [10.04.2017 12:44:09] Seadrive daemon process exited normally with code 0 [10.04.2017 12:44:09] Exiting with error: SeaDrive exited unexpectedly [10.04.2017 12:44:10] seadrive rpc is not ready after 0 retry, abort [10.04.2017 12:44:10] Exiting with error: SeaDrive failed to initialize [10.04.2017 12:44:12] seadrive rpc is not ready after 0 retry, abort [10.04.2017 12:44:12] Exiting with error: SeaDrive failed to initialize
Could it be because our home directories are mounted via NFS (with Kerberos) - if that would be the case - is there a way to change the SeaDrive folder path?