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
In seadrive-gui-log:
[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?
Hmm… We haven’t thought about this situation. We’ll add this ability. At the moment perhaps you can try the cli way first? It’s not much different from the GUI way since almost all functions are in the drive.
Could you maybe think about fusermounting the SeaDrive folder to /run/user/<uid>/?
At least, that’s where the Gnome desktop mounts remote file systems when using gvfs through the Nautilus file manager!
Seadrive is working flawlessly on my headless linux server. I do have a question though.
Does seadrive honour all the fuse options? in particular allow_other would be useful to me. If it does honour them how do I access them? I tried various spells around SEADRIVE_FUSE_OPTS without success.