Dropbox for R6 (x86 only)

btaroli wrote:
Well, I got around the transmissionr6 issue by invoking dpkg manually. ;)

But only because you already ran it through the upload function for there are some additional things that are done there which won't be done by "dpkg" alone. If you don't believe me, just try with an add-on/app you never had installed on the NAS before.

btaroli wrote:
Anyway, I did just use the upload function to install Dropboxmanager and, well I guess you could say the results were mixed. It reports success. But now the web UI for the NAS is dead and the Dropbox service apparently failed to start...

The service "failing to start" is intentional. After a fresh installation, what would you think should be the user accounts Dropbox is automatically enabled for? In my opinion the answer is "None", since it is up to the user (or the admin of the NAS) to define what Dropbox should do for whom. So instead of force-adding a user to the config file in /etc/default, you could have achieved the same by simply starting Dropbox for that particular user using the Dropbox Manager web interface.
The web interface of the NAS itself being broken after installing Dropbox Manager is something I never encountered in the numerous tests I ran on different systems. So I'd be very interested in your findings there and how you fixed those.

btaroli wrote:
dropbox init script seems to keep failing to start since there are no users. Set's "admin" in script but gets reset due to /etc/default/dropbox. I added a username in there, forced a remote reboot and things are happier now.

As said above, this behavior is intentional. As long as the admin of the NAS hasn't defined any users (by clicking the start button for said user) why *should* Dropbox start? By forcing a user in there you also prevented Dropbox Manager from "securing" the users home dir against a "local" installation of Dropbox in the users home dir. Which is what most likely happened on your ReadyNAS and probably led to:

btaroli wrote:
Well, there were for a while anyway... the process spawned for my user died (in defunct state). The admin page shows "start", suggesting it knows it died. Starting it doesn't seem to help. Have gone poking around for a log in /apps/dropboxmanager, /data/Dropbox, /var/log/..., but so far can't seem to locate one... clues?

Try the "Restart All" button, this should also fix the issue you created by manually adding a user name to the config file in /etc/default. As you already noticed, there aren't any logs for the Dropbox daemon doesn't write any. It just writes information to a socket and expects interested applications to pick it up from there. Another reason for any process dying is that you left it running without linking it to any Dropbox account. This is a bug of the Dropbox daemon and nothing Dropbox Manager can fix.

-Stefan