Dropbox for R6 (x86 only)

WhoCares? wrote:
Dropbox Manager remembers the users you as the admin of the ReadyNAS started the Dropbox daemon for in the /etc/default/dropbox file.

OK, and that's how I have been managing them.

WhoCares? wrote:
Dropbox itself however remembers it's state for every user in an encrypted database it puts into the .dropbox directory below the user's home dir.

Which I deleted.

WhoCares? wrote:
Or into /apps/.dropbox for the admin user. Since you didn't wipe this dir on your latest try Dropbox of course maintained stated and remembered that the Dropbox was already linked.

I see /data/.dropbox and /data/.dropbox-master (both of which I did delete), but there is no such /apps/.dropbox on my system.

I'm not sure if you meant to imply it, but after uninstalling and deleting files and re-installing, it did remember to start my user daemon but it was definitely not linked. I had to do that still. That's why I suspected /etc/default/dropbox. But I'll check to see what's left behind after uninstalling again this time.

WhoCares? wrote:
The Dropbox Manager app will *never* wipe either the Dropbox folder or the .dropbox info structure. This is to make sure that a users doesn't accidentally removes his files.

Which is fair, except that I (from past experience in 4.2.x land) always delete the Dropbox folder(s) to avoid data loss when two existing archives try to sync. Had some nasty experiences with that in the past.

WhoCares? wrote:
btaroli wrote: Am I curious enough to try and install the old version to verify if that was the issue? Not at this moment, but ask me later. ;) Well, you can try that if you want to. But I don't think that there's any real benefit in doing so, since the old version is no longer available to users anyway.

Well, I think I'm going another round with 1.0.4 re-install, since the dropbox daemon isn't dropping into the "downloading file list" status now, but it is getting stuck in the sync state at the same file count for hours and hours. And every single time I use the settings UI to stop/start (which I suspect is likely just running /etc/init.d/dropboxmanager), another defunct daemon is left hanging around.