User Tools

Site Tools


linux:dropbox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
linux:dropbox [2018/10/25 13:45]
jansen [Dropbox]
linux:dropbox [2018/10/26 14:37]
jansen
Line 6: Line 6:
 Not only will that prevent quota problems on /home, it will also be faster, because your local copy is actually local. Not only will that prevent quota problems on /home, it will also be faster, because your local copy is actually local.
   * **IMPORTANT**:​ As of October 2018, Dropbox is giving warnings that it will stop working on unsupported filesystems,​ which includes nfs (network file system, eg the /home disk). Two scenarios to solve this:   * **IMPORTANT**:​ As of October 2018, Dropbox is giving warnings that it will stop working on unsupported filesystems,​ which includes nfs (network file system, eg the /home disk). Two scenarios to solve this:
-  - A new setup of Dropbox will by default start in ''/​home''​ and complain. Go into the preferences and move Dropbox to a location on the local disk (''/​data1''​ or ''/​data2''​)+  - A new setup of Dropbox will by default start in ''/​home''​ and complain. Go into the preferences and move Dropbox to a location on the local disk (''/​data1''​ or ''/​data2''​). That should solve the issue and stop the warnings.
   - If you followed earlier advice, and moved ''​~/​Dropbox''​ to a local disk, but kept a symbolic link, the warning will appear since dropbox apparently doesn'​t understand this. Unfortunately,​ you can not simply tell Dropbox where the directory actually is. So here is a series of actions to work around it, and end up with the desired setup: Dropbox on the local data disk, without the link and without complaints   - If you followed earlier advice, and moved ''​~/​Dropbox''​ to a local disk, but kept a symbolic link, the warning will appear since dropbox apparently doesn'​t understand this. Unfortunately,​ you can not simply tell Dropbox where the directory actually is. So here is a series of actions to work around it, and end up with the desired setup: Dropbox on the local data disk, without the link and without complaints
     * Close dropbox to make sure nothing is running     * Close dropbox to make sure nothing is running
Line 15: Line 15:
     * Restart dropbox again. It will now work with the local location (''/​data1/​yourusername/​Dropbox''​)     * Restart dropbox again. It will now work with the local location (''/​data1/​yourusername/​Dropbox''​)
     * If you want, you can now remove the symbolic link from your home directory     * If you want, you can now remove the symbolic link from your home directory
 +  * An alternative method tricks dropbox into seeing another directory as your home, so you can avoid using the nfs mounted home disk. However, using this method, dropbox cannot be started automatically when you log in, you have to use the commandline to start it up, although file manager access will work once started.
 +    * Stop Dropbox if it is already running
 +    * Create the directory where you want the Dropbox files on the local disk, eg ''/​data1/​yourusername''​
 +    * Point HOME to that location, and start installing dropbox: ​ ''​( setenv HOME /​data1/​yourusername ; dropbox start -i )''​
 +    * Next time you log in, repeat this command without the -i option: ''​( setenv HOME /​data1/​yourusername ; dropbox start )''​
   * Disable LAN sync (Dropbox preferences - general tab). It would only be useful to synchronize between computers in the local network, but the computers in our network can share disks through automount, so there just is no point to have Dropbox generate a lot of network traffic to duplicate a feature we already offer (with much greater flexibility,​ and not limited to a single directory of 2 GB).   * Disable LAN sync (Dropbox preferences - general tab). It would only be useful to synchronize between computers in the local network, but the computers in our network can share disks through automount, so there just is no point to have Dropbox generate a lot of network traffic to duplicate a feature we already offer (with much greater flexibility,​ and not limited to a single directory of 2 GB).
   * Do not run Dropbox on multiple desktops at the same time. Dropbox isn't aware of the fact, that a data location like ''/​net/​computername/​something''​ is shared between computers, it will try to synchronize from that location on one computer, to that same location on another computer, potentially overwriting or damaging the files. And again: there is no need to use Dropbox to synchronize between computers in our network ​   * Do not run Dropbox on multiple desktops at the same time. Dropbox isn't aware of the fact, that a data location like ''/​net/​computername/​something''​ is shared between computers, it will try to synchronize from that location on one computer, to that same location on another computer, potentially overwriting or damaging the files. And again: there is no need to use Dropbox to synchronize between computers in our network ​
linux/dropbox.txt ยท Last modified: 2018/10/26 14:37 by jansen