(2013-06-27, 00:27)iRobie Wrote: Thank you for the great script! It's making XBMC much more smooth!
Thanks, glad you find it useful.
(2013-06-27, 00:27)iRobie Wrote: I'm wondering about remotely running this script. It seems like you need to have the remote computer's userdata dir accessible on your local computer. Is that correct?
For some functions, yes, but not all. The following options will require read/write access to Textures13.db: s, S, x, X, f, c, C, nc, lc, lnc, qa, qax, d, r, R, p, P although qa/qax no longer have a dependency on Textures13.db so I'll remove it in the next release.
(2013-06-27, 00:27)iRobie Wrote: Here's what I'm trying to do, and results: (I had this working by mounting the remote userdata with sshfs, but I switched over to OpenElec which doesn't have this)
So the remote "bedroom" client is OpenELEC? What is the local client OS (the one on which you are running the script), and how have you mounted /private/var/mobile/Library/Preferences/XBMC/userdata?
Assuming the remote client is OpenELEC, it will be sharing the Userdata folder as an SMB share. If you are able to mount Userdata on your local machine using SMB (CIFS), you should have read/write access to Database/Textures13.db and be able to run the lc option.
As an example, to mount the OpenELEC Userdata share on Ubuntu 12.10, the following mount command works for me:
Code:
sudo mount -t cifs //10.0.1.25/Userdata /mnt/userdata -o sec=ntlmv2,username=,password=
The "sec=ntlmv2" option is crucial to mounting OpenELEC SMB shares it would seem.
The above command will mount the OpenELEC files so that they are seen by the local system as owned by root, which will mean you need to run the script as root to have full write access. To avoid this, mount the share so that files are owned by a local user, eg. a user with uid=1001 and a gid=1001 meaning you can run the script under the account associated with uid 1001:
Code:
sudo mount -t cifs //10.0.1.25/Userdata /mnt/userdata -o sec=ntlmv2,username=,password=,uid=1001,gid=1001
Use the command "id <username>" to see which id and groups are associated with a specific user.
If I've misunderstood your precise setup let me know and I'll try to come up with another suggestion.