Changes to options on one system, result in changes to another system

[Graham]

... always applies in all circumstances and at all times and applies equally to NextPVR servers and NextPVR clients.

I appear to have got this wrong ... the Boss says that a client and server share the same config.xml so it may be that in a setup with multiple servers and multiple clients (and a momentary loss of concentration), a change on one machine could unexpectedly appear in the config.xml of another machine.

[johnsonx42]

@Lone_Stranger: I'm pretty sure what cncb suggested will be your problem. All the doubt you're getting is because aside from something like this that you've done, there just isn't any mechanism that could possibly produce the result you're seeing. This is surely yet another case of the computer doing exactly what you told it to do, even if you don't remember telling it to do that nor understood all the consequences of it; they're pretty annoying that way.

Are you sure you didn't accidentally set the "DataDirectory" in the Registry to be a network shared directory? I did this at first and got similar unexpected results.

[johnsonx42]

I appear to have got this wrong ... the Boss says that a client and server share the same config.xml so it may be that in a setup with multiple servers and multiple clients (and a momentary loss of concentration), a change on one machine could unexpectedly appear in the config.xml of another machine.

sub mistyped. npvr PC clients do not use the same config.xml as the server, they only share the database. (on the other hand, web clients and nmt/pch clients do use the server's config.xml)

that said, there is a bug (or at least there was). when you first put a client in client mode and give it the shared database path, until you exit and restart the client it continues to operate as if it were a server but operates on the remote database as if it were the local database. the biggest ugly consequence of this is that if you then go back in to Settings->Devices, perhaps to verify your database path, the client will think all the tuners in the database are supposed to be local, notes that it doesn't see them (unless of course they're network tuners), and then flags them all as Not Present. Good luck getting your server to schedule any recordings after that with all the tuners marked Not Present, and Live TV won't work too well either. I reported this bug awhile back, but didn't pursue it further so I don't know if it ever got fixed.

however this is not Lone_Stranger's problem.

[sub]

sub mistyped. npvr PC clients do not use the same config.xml as the server, they only share the database. (on the other hand, web clients and nmt/pch clients do use the server's config.xml)

I didn't really mistype, but maybe I wasn't clear enough. On client PCs, they have their own config.xml, and the settings aren't shared with other machines, but there is some read directly from the server's config.xml. I couldn't have seen the very slim possibility that in this type of setup some settings may have been updated on the server. A user reported this in the past, but we never reproduced it. I probably shouldn't have mentioned that, because it just confuses issues for people. Lone_Strangers not using a client/server setup though, so that shouldn't the issue here.

As you've mentioned, data directory on a shared drive is most likely cause.