Well the problem here is that this is dependent upon the assumption that you are mounting your recordings in the same place on all your backends and frontends. This is fine if you only have one backend and one frontend, but really makes for a troublesome situation otherwise.
Let me present two situations that automating this breaks entirely: (1) Machine A, master backend mounted at /var/lib/mythtv/recordings locally Machine B, slave backend mounted at /var/lib/mythtv/recordings locally Neither machine A or machine B clearly have each others recordings mounted. Now you add Machine C, a frontend. Well so what do you do about mounting these recordings? You can clearly only mount one machine's recordings. (2) Machine X, master backend mounted at /var/lib/mythtv/recordings/X Machine Y, slave backend mounted at /var/lib/mythtv/recordings/Y Machine Z, frontend Now on Machine Z, you can go and make the directories /var/lib/mythtv/recordings/X and /var/lib/mythtv/recordings/Y, and then mount them there no problem. The issue then is what do you put into the settings database? You can't just say /var/lib/mythtv/recordings, because it's expecting to find the recordings at wherever you define the RecordFilePrefix to be. ---- The only possible solution that I forsee would involve a patch upstream that would change the behavior of the RecordFilePrefix, as well as how these recordings are then accessed. -- mytharchive fails with python error https://bugs.launchpad.net/bugs/118700 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
