2005-04-13, 00:50
philled: yes, i meant that the hostname populated in the recorded table in the myth database may not be correct and if you have %h in the path prefix, it could build the path incorrectly. the recorded hostname and the smb path prefix do not have to match. the only time you may want to use %h is if you have multiple servers running the mythbackend software (this is untested since i only have one myth server). here is an example of my setup:
- recorded hostname 'banshee'
- samba server runs on banshee advertises "mythtv" service which is a folder containing nuv and live tv ring buffer files
- path on the filesystem where nuv and live tv ring buffer are created is actually /myth/tv/
my recorded prefix is "smb://%h/mythtv". i could also specify a prefix of "smb://10.1.1.5/mythtv" assuming the ip of banshee is 10.1.1.5. note: i also have a dns server running for my lan...
when you copy a file, the only path that is used from the settings is the local path. so if your recorded prefix or live tv prefix is setup incorrectly, it won't affect the copy. copying files using smb.py was extremely slow so i rewrote it to use the myth protocol instead.
- recorded hostname 'banshee'
- samba server runs on banshee advertises "mythtv" service which is a folder containing nuv and live tv ring buffer files
- path on the filesystem where nuv and live tv ring buffer are created is actually /myth/tv/
my recorded prefix is "smb://%h/mythtv". i could also specify a prefix of "smb://10.1.1.5/mythtv" assuming the ip of banshee is 10.1.1.5. note: i also have a dns server running for my lan...
when you copy a file, the only path that is used from the settings is the local path. so if your recorded prefix or live tv prefix is setup incorrectly, it won't affect the copy. copying files using smb.py was extremely slow so i rewrote it to use the myth protocol instead.