Tags

Sites I Read

In our department, all of our home directories are stored on a central
fileserver and mounted to each machine as needed. Windows workstations get a
network drive rooted at /home/<user> and linux workstations automount /home
on /misc/home as needed. Many of our faculty use Dropbox as a way to access
their files from home, on vacation, wherever they need to be. This can cause a
problem for us with dropbox because we also provide terminal server access (from
anywhere). We have had trouble with users installing dropbox into their home
directories, and running it on more than one department workstation (or our
terminal server). This can cause trouble because there are multiple dropbox
clients updating the same directory on disk. I decided to do a centralized
dropbox install on our fileserver which can be made available to anyone who
would like to link their dropbox account to the department fileserver.

Post-Setup

After the dropbox distribution is in place, the init script is installed and the
users are configured, it is time to start each of the daemons.

root@fileserver# service dropbox start
This client is not linked to any account...
Please visit https://www.dropbox.com/cli_link?host_id=abcdef1234567890 to
link this machine.

At this point, dropbox will print registration URLs to stdout. For now, it is
important to do one user at a time to match each registration URL to a user.

TODO

Automate dropbox user addition

Eventually I would like to build this into our soon-to-be-released selfserv
application. It would be trivial to modify this script to check a UNIX group
rather than an initscript array to get user information.

Capture the output from each daemon to separate logfiles in order to track
down issues

Use pydropboxvalues
to capture registration URL and present it to the user on the selfserv signup page