Interplay of config.xml files on PC Client

[gkreis]

How do the config.xml (and other settings) interplay between those on the server and the PC Client? For instance, I want to disable the starting of the recording service when leaving config on the PC Client. Also, I don't want the gbpvr tray app to start. Does anyone know what I need to put into the config.xml to do this? Provided there is something that can do this, will I be able to disable it on the PC Client without affecting the start of the service on the server?

If I install a plugin on the server, does it also have to be installed on the client? Will the plugins automatically inherit the configurations on the client that are set on the server?

I am confused about the interaction.

[nightwalker]

from what i can tell so far, both machines are separate, in that they have their own configurations and settings. I think it's just the database and directories that are shared, and of course the TV tuner(s). Any plug ins that you want to run on both need to be installed on both.

I'm hoping that as time goes on plug in authors will allow configurations and databases to be shared, to keep the machines in sync with one another.

I'd like to see the ability to have TV cards on multiple machines. A local TV card is a lot better and quicker on the local machine, especially for channel changes.

[sub]

For instance, I want to disable the starting of the recording service when leaving config on the PC Client. Also, I don't want the gbpvr tray app to start. Does anyone know what I need to put into the config.xml to do this?

There is no setting to change this. It always tries to start recording service when you exit the config app. I may add a setting in a future release.

If I install a plugin on the server, does it also have to be installed on the client?

No.

Will the plugins automatically inherit the configurations on the client that are set on the server?

No.

[gkreis]

Does it make sense that if I don't define a tuner that the recording service should automatically not be activated? Is that a good rule?