Multiple config files for user and service accounts?

[snakyjake]

Are there potential problems running QBT as a daemon service (e.g. qbtuser) for the webui, and also logging in to the GUI version from a different account (e.g. jake)?
Or if the webui isn't running, but I start the GUI version?

I'm suspicious because I noticed QBT is storing config/resume data under the user accounts.  And having multiple config/resume files would cause me problems.  In the example above, notice the webui and gui run under difference user accounts.

Thanks,
Jake

[ciaobaby]

The webUI uses a login that is wholly internal to the client, rather than a host machine user account.

[snakyjake]

Restating the question:

I presume when logging into the WebUI it uses the daemon user configuration.

But what happens when I log into the GUI version?

I presume when I log into the GUI version that I will be using a different configuration. 

If this is true, then this caused me problems, and may cause other people the same problem.

[ciaobaby]

No, No and No.

qbittorrent runs at all times in the context of the user the the machine starts up as.

The WebUI UI does NOT start an instance of the client it will connect to the client that is already running and is listening on the specified port at the URL or IP that was requested.

Starting the GUI should NOT start a new instance of the client, normally there is only one configuration that the client runs under and only one instance of the client, can be running at anyone time, on any one machine for any one user. Known as a MUTEX (Mutually Exclusive).

Any problems that you are having with the client running in a service context is going to depend on how that context is set up.

[snakyjake]

What happens when the service isn't started, and I log in from the GUI (as jake)?

Will QBT start as a GUI client using the login credentials (jake), using different credentials from the service account (qbtuser)? 

[ciaobaby]

You don't 'login' to the GUI, you login as a machine user and the GUI application is part of that user profile, there is no log-in interaction between the GUI and the down-loader part of the application, it will simply connect to whatever instance of the down loader application is running and available, if a running instance is not found it will start one, complete with separate configuration files and folders for that user.

In principle, this should never be a problem because a remote installation would never normally have a GUI interface connecting to it.