Use qBittorrent in a dualboot Linux/Windows

[krypton]

I using both Windows and Linux in dualboot (Windows 7 Ultimate 64-bit - Linux Mint 15 "olivia" - MATE 64-bit), I want to ask if is possible to share the session state between the qBittorent versions of the respective operating systems. The current version of qBittorent (v3.0.11) is already installed in the two operating systems.
I explain me better with an example, if in Windows I have downloaded multiple files that are at any percentual of downloading, can I resume the download status of these files without loss of data in Linux (or viceversa)?
I have thinked to do a mount of the Windows partition, where the configuration data are stored, in an autoexec script which is called by the rc.local file of Linux in a way like that:

Content of the rc.local file:

Code: Select all

~/autoexec/Config.sh

exit 0

Content of Config.sh script:

Code: Select all

#.config
mount --rbind /media/disk_c/Users/<username>/AppData/Roaming/qBittorrent/	~/.config/qBittorrent/
#.local
mount --rbind /media/disk_c/Users/<username>/AppData/Local/qBittorrent/		~/.local/share/data/qBittorrent

note: the association between the label disk_c and the physical disk is done in the /etc/fstab file: 

Code: Select all

# C:\ disk of Windows 7 
UUID="F800419500415BAE" /media/disk_c ntfs-3g  defaults,windows_names,locale=en_US.utf8  0 0

But here come the problems, because the configuration files of the two qBittorent versions have different extensions: .conf versus .ini
qBittorrent.ini and qBittorrent.conf aren't problematic, because I have doing a comparison and the configuration strings are similar.
The really big problem is the difference between qBittorrent-resume.ini versus qBittorrent-resume.conf.
I don't know if a rename of the extension of this file at boot time is a right operation.

[sledgehammer_999]

I propose a similar hack since something like this isn't supported by qBittorrent:

When on Linux symlink the BT_backup folder of qbittorrent to the one found on the windows partition. This is the only thing that you can truly share without problem. It saves the .torrent files and the .fastresume files. The latter ones are responsible for keeping the progress of each torrent. The other interesting thing is the qbittorrent-resume.ini/.conf file. This file saves the save-path for each torrent(among other things). This cannot be shared, because the Windows version will not be able to find the linux-saved path and vice versa.

So everytime you add a new torrent in linux and the switch to windows, the new torrent will be picked up automatically but because it won't find a suitable entry in qbittorrent-resume it will start to download to the default location, the fastresume will get rejected(no files at the default location) and the torrent will start downloading from ) 0% percent at the default location.

So basically you cannot achieve this, without doing a "forced rechecK" on new torrents in the other OS(after pointing it to the correct save path).
But once the 2 clients know, about the torrents and where they are actually saved the fastresume will work and you won't have to do a force recheck.

[AzureCerulean]

BTW: job so far.


so with the storage path and file name ..

create sym/hard links to the files and use different names.

IE

ln -s qbittorrent.ini qbittorrent.conf

for all of its files.

with the paths,

In Linux, Qbittorrent defaults to  the  users home directory

If you reference

C:\Users\{windows user}\qbittorrent\Torrents

Linux would be seen as the

/home/{Linux user}/c:/users/{windows user}/qbittorrent/Torrents

only mount/bind your Windows drive to your home directory, using it 's drive letter


mkdir /home/{linux user}/C:

ensure the user has the appropriate permission to access/change files

mount – rbind/{windows_mnt}/home/{linux user}/C:

the only problem encountered so far : "special" characters and how they are handled  when a torrent/magnet uses a file/folder/name that would not be acceptable in Windows, but is in  Linux there will be issues.

but again, you can always create links to the real files with new names.